Analytics
nowpattern.com
Provides scorecards, Brier track records, calibration passports, and failure-pattern registries for evaluating forecasting and agent-claim accuracy.
ENDPOINT 1
https://nowpattern.com/mcp
MCP server metadata
- Name
- nowpattern-calibration-notary
- Version
- 1.0.0
Known tools 6
get_agent_claim_scorecardSealed-claim arena scorecard (dry-run; demo- agents excluded from skill claims by rule).
Inferred read-onlyget_calibration_passportCalibration passport: per-genre reliability of the notary's own published forecasts.
Inferred read-onlyget_failure_patternsStructured failure-pattern registry (MISS causes) — the lessons layer no score-only leaderboard publishes.
Inferred read-onlyget_verified_outcomesSourced, independently re-derivable forecast outcomes (every row carries a public source URL; honest HIT/MISS including the operator's own misses).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.nowpattern-calibration-notary]
url = "https://nowpattern.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"nowpattern-calibration-notary": {
"type": "http",
"url": "https://nowpattern.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: nowpattern-calibration-notary
Remote MCP URL: https://nowpattern.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"nowpattern-calibration-notary": {
"url": "https://nowpattern.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"nowpattern-calibration-notary": {
"type": "http",
"url": "https://nowpattern.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "nowpattern-calibration-notary",
"transport": "streamable-http",
"url": "https://nowpattern.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.