mcp-registry/app.surewhynot.quartermaster/quartermaster · v1.6.0
As of 2026-10-26 16:38 UTC, the Surewhynot Quartermaster Quartermaster MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
x402 toolkit for AI agents: paid web, AI, and Base chain tools per call in USDC. Free tools too.
Point your MCP client at this streamable-http endpoint: https://quartermaster.surewhynot.app/mcp
49 of 49 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
49 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
63 parameter(s) across 38 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
4 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 38 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fapp.surewhynot.quartermaster%2Fquartermaster/fixes
{
"name": "base_token_info",
"description": "ERC-20 name, symbol, decimals, total supply for a token on Base. Costs $0.001.",
"inputSchema": {
"type": "object",
"required": [
"address"
],
"properties": {
"address": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "base_usdc_transfers",
"description": "Recent USDC transfers (in and out) for an address on Base. Costs $0.002.",
"inputSchema": {
"type": "object",
"required": [
"address"
],
"properties": {
"limit": {
"type": "integer"
},
"address": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "describe_image",
"description": "[AI] AI vision: describe a public image URL, including visible text. Costs $0.005.",
"inputSchema": {
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string"
},
"prompt": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/app.surewhynot.quartermaster/quartermaster"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/app.surewhynot.quartermaster/quartermaster"}) over MCP.
settlement_assurance ~240 tokenspayment_proof ~195 tokensx402_audit ~177 tokensx402_router ~173 tokensx402_simulate ~173 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fapp.surewhynot.quartermaster%2Fquartermaster?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fapp.surewhynot.quartermaster%2Fquartermaster?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.surewhynot.quartermaster%2Fquartermaster.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.surewhynot.quartermaster%2Fquartermaster.svg :target: https://glimind.com/server/mcp-registry%2Fapp.surewhynot.quartermaster%2Fquartermaster?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:67a0a791992f93fc…, first seen 2026-10-17, included at leaf 11153 of 74,160. Version history · verify what your client received.
Compare: most reliable data servers · most reliable finance servers · most reliable blockchain servers · most reliable ml servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 16:38 UTC, the Surewhynot Quartermaster Quartermaster MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Surewhynot Quartermaster Quartermaster MCP server advertises 49 tools, including base64, base_allowance, base_contract, base_token_info, base_usdc_transfers.
Point your MCP client at this streamable-http endpoint: https://quartermaster.surewhynot.app/mcp
Glimind scanned all 49 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.