Nerf Watch
REMOTE · TOKENUSAGE.DEV
Daily Nerf Watch scores for Claude and GPT models on one private, code-graded suite. Read-only.
Available components
Last scanned (16 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 23 Oct 2026.
Category AI and Machine Learning
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 409 tokens (~204/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 21 Oct 26 73
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Probed https://tokenusage.dev/mcp/nerfwatch
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tokenusage.dev | CN=WR3,O=Google Trust Services,C=US | 7 Oct 2026 | 5 Jan 2027 | RSA 2048 | SHA256-RSA | e379fb245feea5ba0a095028385ac8a8 |
| SANs: tokenusage.dev, www.tokenusage.dev | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
| CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 1 Sept 1998 | 28 Jan 2028 | RSA 2048 | SHA1-RSA | 40000000001154b5ac394 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tokenusage.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| tokenusage.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31556926 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tokenusage.dev/mcp/nerfwatch | Verified | 200 | |
| http (plaintext) | http://tokenusage.dev/mcp/nerfwatch | HTTPS enforced | 301 | https://tokenusage.dev/mcp/nerfwatch |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_nerfwatch_history Nerf Watch history ~149
Retained public Nerf Watch score history for one model, oldest first, including each point's suite version. The required model id is available from get_nerfwatch_scores. Missing days are missing, not zero; comparisons are within one suite version. A lower score is a lower score on this suite, not proof that a provider changed a model. Unofficial, not affiliated with OpenAI or Anthropic. Source: https://tokenusage.dev/nerfwatch
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | yes | A model id from get_nerfwatch_scores: 1 to 64 lowercase letters, digits, dots, underscores or hyphens, starting with a letter or digit. |
| Name | Type | Req | Description |
|---|---|---|---|
| dataUpdatedAt | string|null | yes | When the newest retained run across the dataset was stored, ISO 8601 UTC; null without runs. This is dataset metadata, not a timestamp for this model alone. |
| generatedAt | string | yes | When the cached data was read, ISO 8601 UTC; the cache TTL is 300 seconds from read start. |
| history | array | yes | Retained points, oldest first, including older suite versions; days without a run are missing, not zero. |
| historyDays | integer | yes | The returned retention bound per model; clients read this setting rather than assuming 366. |
| model | string | yes | The selected model id. |
| name | string | yes | The selected model's published display name. |
| provider | string | yes | The selected model's published provider name. |
| source | string | yes | The fixed credit URL, https://tokenusage.dev/nerfwatch. When showing the data to other people, show Data: tokenusage.dev linked to this URL on the same screen or in the same message. Personal use nee… |
No examples provided.
get_nerfwatch_scores Nerf Watch scores ~117
Latest public Nerf Watch scores, previous runs, changes and baselines for at most 100 models, ordered by provider, name and model id. No arguments. Histories are available through get_nerfwatch_history. Scores and changes are rounded to two decimals; comparisons are within one suite version. A lower score is a lower score on this suite, not proof that a provider changed a model. Unofficial, not affiliated with OpenAI or Anthropic. Source: https://tokenusage.dev/nerfwatch
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| baselineDays | integer | yes | The UTC-day window before each latest run used for its baseline; this is the returned setting, not a fixed client assumption. |
| dataUpdatedAt | string|null | yes | When the newest retained run was stored, ISO 8601 UTC; null without runs. This is distinct from response generation time. |
| flatPoints | number | yes | An absolute change versus baseline at or below this returned setting is flat. |
| generatedAt | string | yes | When the cached data was read, ISO 8601 UTC; the cache TTL is 300 seconds from read start. |
| minBaselineRuns | integer | yes | The minimum number of same-suite runs needed for a baseline; this is the returned setting. |
| models | array | yes | Models in source order: provider, name and model id; empty before the first run. |
| source | string | yes | The fixed credit URL, https://tokenusage.dev/nerfwatch. When showing the data to other people, show Data: tokenusage.dev linked to this URL on the same screen or in the same message. Personal use nee… |
No examples provided.
How do I install the Nerf Watch MCP server?
Nerf Watch is a hosted endpoint at https://tokenusage.dev/mcp/nerfwatch, 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.
remote · tokenusage.dev
claude mcp add --transport http dev-tokenusage-nerfwatch 'https://tokenusage.dev/mcp/nerfwatch'
What is the Nerf Watch MCP server?
Nerf Watch is an MCP server listed in the public MCP registry as dev.tokenusage/nerfwatch. Daily Nerf Watch scores for Claude and GPT models on one private, code-graded suite. Read-only. This page covers its hosted endpoint (https://tokenusage.dev/mcp/nerfwatch).
Is the Nerf Watch MCP server safe to use?
Nerf Watch 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 Nerf Watch MCP server expose?
Nerf Watch exposes 2 tools: get_nerfwatch_scores, get_nerfwatch_history. Their descriptions and schemas cost roughly 266 tokens of context every time the server is loaded.
Does the Nerf Watch MCP server require authentication?
No. We connected to Nerf Watch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nerf Watch MCP server still maintained?
Nerf Watch is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.