mcp-registry/io.github.noahmchugh/stinkyboy-bodega · v1.0.0
Also listed as mcp-registry/io.github.noahmchugh/stinkyboy · primary listing: mcp-registry/io.github.noahmchugh/stinkyboy
As of 2026-10-27 04:25 UTC, the Noahmchugh Stinkyboy Bodega MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.3% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 506.5 hours.
One integration, one wallet. Thousands of callable tools, paid per call in USDC via x402.
Point your MCP client at this streamable-http endpoint: https://mcp.stinkyboy.co/mcp
6 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
13 parameter(s) across 6 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 →
6 of 6 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 →
1 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 →
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. 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. 6 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.noahmchugh%2Fstinkyboy-bodega/fixes
{
"name": "call_tool",
"description": "Execute any catalog tool by id. Payment is charged on success only.",
"inputSchema": {
"type": "object",
"properties": {
"inputs": {
"type": "string"
},
"tool_id": {
"type": "string"
}
}
}
}{
"name": "catalog_search",
"description": "Search all catalog tools. synthesize=true (default) compiles a missing tool on the spot instead of returning a miss.",
"inputSchema": {
"type": "object",
"properties": {
"query": {
"type": "string"
},
"filters": {
"type": "string"
},
"synthesize": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "create_and_call",
"description": "State the desired outcome with real inputs; the immediate compiler builds the missing tool and runs it in the same session.",
"inputSchema": {
"type": "object",
"properties": {
"inputs": {
"type": "string"
},
"outcome": {
"type": "string"
},
"path_hint": {
"type": "string"
},
"callback_url": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}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/io.github.noahmchugh/stinkyboy-bodega"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.noahmchugh/stinkyboy-bodega"}) over MCP.
create_and_call ~76 tokenscatalog_search ~69 tokensget_quote ~52 tokenstool_detail ~51 tokenscall_tool ~49 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%2Fio.github.noahmchugh%2Fstinkyboy-bodega?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.noahmchugh%2Fstinkyboy-bodega?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.noahmchugh%2Fstinkyboy-bodega.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.noahmchugh%2Fstinkyboy-bodega.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.noahmchugh%2Fstinkyboy-bodega?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:8b4d87f2bc7c0bef…, first seen 2026-10-17, included at leaf 4345 of 77,349. Version history · verify what your client received.
Compare: most reliable other servers · most reliable search servers · most reliable code servers · most reliable finance servers · most reliable data 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-27 04:25 UTC, the Noahmchugh Stinkyboy Bodega MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.3% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 506.5 hours.
Noahmchugh Stinkyboy Bodega MCP server advertises 6 tools, including call_tool, catalog_search, create_and_call, get_quote, my_spend.
Point your MCP client at this streamable-http endpoint: https://mcp.stinkyboy.co/mcp
Glimind scanned all 6 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.