# com.robinsaige/verifier (remote · robinsaige.com)

MCP tool observatory: do registry servers answer, and are their answers true? No key.

- Trust score: 74/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- remote · `robinsaige.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-robinsaige-verifier/robinsaige.md), [page](https://verifymcp.io/servers/com-robinsaige-verifier/robinsaige)

## Channel facts

- Endpoint: `https://robinsaige.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-26.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1298 tokens (~162/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 71% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the com.robinsaige/verifier MCP server?

com.robinsaige/verifier is a hosted endpoint at https://robinsaige.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-robinsaige-verifier 'https://robinsaige.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-robinsaige-verifier": {
      "url": "https://robinsaige.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-robinsaige-verifier": {
      "type": "http",
      "url": "https://robinsaige.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-robinsaige-verifier]
url = "https://robinsaige.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-robinsaige-verifier": {
      "type": "remote",
      "url": "https://robinsaige.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-robinsaige-verifier --url 'https://robinsaige.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-robinsaige-verifier:
    url: "https://robinsaige.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-robinsaige-verifier": {
      "Transport": "http",
      "Url": "https://robinsaige.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-robinsaige-verifier -t streamable-http -u 'https://robinsaige.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-robinsaige-verifier": {
      "type": "http",
      "url": "https://robinsaige.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-26 (score 74, 0)

- [security] Stability: 0.97 → pass

### 2026-09-25 (score 74, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-14 (score 74, +4)

- [security improvement] Stability: fail → pass

### 2026-09-11 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 65 to 69.

### 2026-09-09 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 59 to 62.

### 2026-09-07 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 52 to 55.

### 2026-09-05 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 45 to 49.

### 2026-09-03 (score 66, +43)

- [security regression] Stability: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100

## MCP tools (8)

### `registry_pulse` (~92 tokens)

Call this FIRST for the state of the MCP tool ecosystem in one shot: how many servers exist, how many actually answer a real handshake, how many are behind a login, the largest costume-farm concentration, AND the Tier-2 truth summary (how many server answers were re-derived against a public primary source and matched). Every number is re-derivable; grades observed/reported/derived. No arguments.

### `should_i_use` (~179 tokens)

THE GATE — call this before your agent depends on a tool you don't already trust. Give an exact server registry name and get a one-word verdict — allow / warn / block — with the reason, plus the full rating underneath. 'block' = dead/unreachable/costume-farm-shaped, don't depend on it; 'warn' = usable but look first; 'allow' = safe to depend on. If you have a NEED not a name, use find_tools; if you have a fuzzy name, use resolve_server_name. Argument: name, e.g. 'com.trimtabist/us-tariff-ledger'.

Input parameters:

- `name` (string): exact registry name, e.g. io.github.you/your-mcp
- `names` (array): batch form: vet a whole config at session start (max 20)

### `find_tools` (~238 tokens)

Find and RANK the trustworthy tool for a NEED. Describe the task in plain words ('screen a company for sanctions', 'US tariff data', 'vessel tracking') — the search is full-text over tool names AND their stored descriptions (stemmed, BM25-ranked), so your words need not appear in any tool's name. Servers come best-rated first, and EACH ROW carries its verdict (allow/warn/block), cluster, distinctiveness and the matching tool names, so you can pick without a second call. Alive, non-costume, current-protocol servers rank on top; dead / costume-farm / walled ones sink. Argument: need.

Input parameters:

- `free_only` (boolean): exclude servers that demand payment at the handshake
- `max_latency_ms` (integer): only servers at or under this probe latency
- `nature` (string): only servers whose dominant tool nature is this (see robinsaige.com/verification)
- `need` (string, required): what the tool should do, in plain words
- `open_only` (boolean): exclude auth-walled servers
- `verdict` (string): only servers with this verdict

### `resolve_server_name` (~91 tokens)

Resolve a partial or misspelled server name to its EXACT registry id before calling should_i_use / check_server. Matches a fragment against registry NAMES only (not capabilities — for 'which tool does X' use find_tools). Returns candidate exact names with each one's latest liveness outcome. Empty query rejected.

Input parameters:

- `query` (string, required): a fragment of a registry name, e.g. 'tariff'

### `check_server` (~165 tokens)

The FULL evidence behind the verdict for ONE server, by exact registry name — call should_i_use first for the one-word decision; call this when you want the whole record. Leads with the verdict (allow/warn/block), then the `rating` grouped as REACH (answers, latency vs population, protocol, auth), USE (tool count vs population, capability breadth, harness readiness) and TRUST (costume-farm?, duplicate inventory?, verifiability grade, drift / rug-pull, and where checkable whether its ANSWERS are true vs a public primary), a cluster tag, a distinctiveness score, and an explicit not_claimed block. Argument: name.

Input parameters:

- `name` (string, required): exact registry name, e.g. io.github.you/your-mcp

### `report_call` (~179 tokens)

AFTER your agent calls a tool, fire-and-forget how it went — success/failure, latency, cost — so the observatory accumulates realized reliability (the one thing outside-in probing can't see: did it actually work for a real call). Anchored against our own probe: a 'worked' report on a server we saw dead is discarded. Does NOT change the current rating yet (probing stays load-bearing) — this is accumulate-ahead-of-demand. Args: server (required), tool, ok, latency_ms, cost_tokens, call_hash (a hash binding the report to a real call).

Input parameters:

- `call_hash` (string)
- `cost_tokens` (integer)
- `latency_ms` (integer)
- `ok` (boolean)
- `server` (string, required): exact registry name
- `tool` (string)

### `changes_since` (~70 tokens)

What changed in the tool economy since a date: verdict flips, deaths, revivals, new servers, confirmed drift — the census diff as data. Poll this weekly to keep a local view current without re-crawling.

Input parameters:

- `since` (string): YYYY-MM-DD; omit for the whole latest diff

### `list_findings` (~62 tokens)

The observatory's ruled findings — each with its claim and its falsification test — plus the public corrections log (what we published, then corrected, never deleted). Call this to cite what has been established, or to see where we were wrong. No arguments.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-robinsaige-verifier/robinsaige#diagnostics

## Score history

- 2026-09-26: 74
- 2026-09-25: 74
- 2026-09-24: 74
- 2026-09-23: 74
- 2026-09-22: 74
- 2026-09-21: 74
- 2026-09-20: 74
- 2026-09-19: 74
- 2026-09-18: 74
- 2026-09-17: 74
- 2026-09-16: 74
- 2026-09-15: 74
- 2026-09-14: 74
- 2026-09-13: 70
- 2026-09-12: 70
- 2026-09-11: 70
- 2026-09-10: 69
- 2026-09-09: 69
- 2026-09-08: 68
- 2026-09-07: 68
- 2026-09-06: 67
- 2026-09-05: 67
- 2026-09-04: 66
- 2026-09-03: 66
- 2026-09-02: 23
- 2026-09-01: 65
- 2026-08-31: 64
- 2026-08-30: 64
- 2026-08-29: 63
- 2026-08-28: 63

## Common questions

### What is the com.robinsaige/verifier MCP server?

com.robinsaige/verifier is an MCP server listed in the public MCP registry as com.robinsaige/verifier. MCP tool observatory: do registry servers answer, and are their answers true? No key. This page covers its hosted endpoint (https://robinsaige.com/mcp).

### Is the com.robinsaige/verifier MCP server safe to use?

com.robinsaige/verifier scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the com.robinsaige/verifier MCP server expose?

com.robinsaige/verifier exposes 8 tools: registry_pulse, should_i_use, find_tools, resolve_server_name, check_server, and 3 more. Their descriptions and schemas cost roughly 1,076 tokens of context every time the server is loaded.

### Does the com.robinsaige/verifier MCP server require authentication?

No. We connected to com.robinsaige/verifier without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the com.robinsaige/verifier MCP server still maintained?

com.robinsaige/verifier is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://robinsaige.com/mcp
- Website: https://robinsaige.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-robinsaige-verifier/robinsaige.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-robinsaige-verifier/robinsaige.json
- HTML version of this page: https://verifymcp.io/servers/com-robinsaige-verifier/robinsaige