get_verification
Community verification on a registry organization: how many of its public findings have signals, how many are community confirmed, contested or kept after review, and each signed finding's handle with its state (open, community_confirmed, contested, kept), confirmations, flags, corrections and owner (confirmed or disputed by the organization itself). get_organization carries the same as vf on each node. Public.
Parameters
- refstringrequired
The organization's registry ref
max 200 chars
Example call
Agents call tools by name; you rarely write this by hand. It is here so you can test the server from a shell or your own code.
{
"name": "get_verification",
"arguments": {
"ref": "acme-builders-3f2a9c1d"
}
}Response
The result is one text content block holding this JSON (abbreviated here). Errors come back with isError: true and a message such as Error 401: … or Invalid input: ….
{
"ref": "acme-builders-3f2a9c1d",
"findings": 42,
"signed": 2,
"states": {
"community_confirmed": 1,
"contested": 1,
"kept": 0,
"open": 0
},
"items": [
{
"h": "comp:3f2a9c1d",
"l": "HubSpot",
"state": "community_confirmed",
"confirmations": 3,
"flags": 0,
"corrections": 0,
"owner": null
}
]
}Over REST
The same call without MCP: GET/api/v1/orgs/:ref/verification