Your read only MCP server blog 299

Lead Story · OCT 2

Inside MCP for Wikidata Candidate Search Limits

Candidate search limits sound like a small implementation detail until you have to trust the output. Then they become one of the most important design choices in the whole system. That is especially true in entity resolution work, where the difference between "probably right" and "provably inspectable" decides whether a match can be used downstream at all. The open source project often described as Wikidata + Google Knowledge Graph MCP takes a very specific stance here.

Continued inside

Read the full column

Analysis · OCT 2

A Closer Look at Inspectable Evidence in MCP for Wikidata

The most interesting thing about recent tooling around Wikidata is not that it helps a model find an entity faster. Search speed is useful, but it is not the hard part. The hard part is trust. If an agent links a person, company, place, or work to the wrong Wikidata item, the mistake does not stay local. It tends to spread into downstream records, summaries, and decisions. That is why inspectable evidence matters. A good MCP server for knowledge work should do more than

Dispatch · OCT 1

AUTO_MATCH, HOLD, AMBIGUOUS, and NO_CANDIDATE in MCP for Wikidata

Entity resolution looks simple until you have to trust it. Anyone who has tried to map a local catalog, CRM, newsroom archive, research database, or product knowledge base to Wikidata knows where the pain starts. Names collide. Labels are incomplete. Dates are missing. Places change names. Organizations merge, split, or rebrand. A human can often sense the difference between a plausible match and a dangerous one. Software needs firmer rules. That is what makes the res