MCP.Market

Calibration Routing MCP server

online · 100% uptime
by nao1234g·io.github.nao1234g/calibration-routing·v1.0.0
No reviews yet

Route tasks by measured judgment quality: third-party-verified, Brier-based calibration records.

B83/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Calibration Routing yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Calibration Routing tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1249ms; handshake note: [ { "code": "invalid_union", "errors": [ [ { "code": "invalid_value", "value20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 61 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Calibration Routing compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
520 ms
faster than 28% of 30,031 servers

Install Calibration Routing in Claude Code, Cursor or VS Code

claude mcp add --transport http calibration-routing https://nowpattern.com/calibration-routing/route
Add to Cursor

What the publisher says

From the Calibration Routing repository's README, as published. We do not edit it. Read it on GitHub

nowpattern-calibration-routing (MCP)

Query a counterparty's MEASURED judgment quality before delegating.

Third-party-resolved, OTS-sealed calibration records. Read-only. Money OFF. Default-deny on unverified candidates. The operator's own losses are published (notary honesty doctrine).

Endpoints

  • Descriptor: https://nowpattern.com/.well-known/calibration-routing.json
  • Route (POST JSON): https://nowpattern.com/calibration-routing/route
  • Discovery index: https://nowpattern.com/.well-known/mcp.json

Zero-trust verification (3 lines, no account, offline)

curl -O https://nowpattern.com/.well-known/rjp/genuineonlyv1.json curl -O https://nowpattern.com/.well-known/rjp/rjpverify.py python rjpverify.py genuineonlyv1.json

Recomputes the published Brier aggregate from the sealed records inside the bundle. Honesty context included: genuine-only segment n=173, mean Brier 0.3096 vs 0.2117 base rate, 74.93% provenance contamination quarantined and disclosed, Hosmer-Lemeshow / Murphy-decomposition audit attached.

License

Data: CC BY 4.0 with attribution to nowpattern.com. Verifier: MIT.

Nothing above is checked by us. What we check is on the safety report.

Calibration Routing: common questions

Is Calibration Routing MCP server safe?
Mostly: it is graded B (83/100). Read the Calibration Routing safety report
How do I install Calibration Routing?
It runs remotely at nowpattern.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Calibration Routing need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Calibration Routing maintained?
The last commit was 101 days ago (2026-07-26). The latest release is v1.0.0.
Is Calibration Routing up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Calibration Routing compare with other MCP servers?
safety score 83/100 (higher than 65% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 520 ms (faster than 28% of 30,031 servers). Full comparison.