Stinkyboy Bodega
REMOTE · MCP.STINKYBOY.CO · SCANNED OCT 2
One integration, one wallet. Thousands of callable tools, paid per call in USDC via x402.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Stinkyboy Bodega MCP server?
Stinkyboy Bodega is a hosted endpoint at https://mcp.stinkyboy.co/mcp, 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 · mcp.stinkyboy.co
claude mcp add --transport http noahmchugh-stinkyboy-bodega 'https://mcp.stinkyboy.co/mcp'
{
"mcpServers": {
"noahmchugh-stinkyboy-bodega": {
"url": "https://mcp.stinkyboy.co/mcp"
}
}
} {
"servers": {
"noahmchugh-stinkyboy-bodega": {
"type": "http",
"url": "https://mcp.stinkyboy.co/mcp"
}
}
} [mcp_servers.noahmchugh-stinkyboy-bodega] url = "https://mcp.stinkyboy.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"noahmchugh-stinkyboy-bodega": {
"type": "remote",
"url": "https://mcp.stinkyboy.co/mcp",
"enabled": true
}
}
} openclaw mcp add noahmchugh-stinkyboy-bodega --url 'https://mcp.stinkyboy.co/mcp' --transport streamable-http
mcp_servers:
noahmchugh-stinkyboy-bodega:
url: "https://mcp.stinkyboy.co/mcp" {
"McpServers": {
"noahmchugh-stinkyboy-bodega": {
"Transport": "http",
"Url": "https://mcp.stinkyboy.co/mcp"
}
}
} assistant mcp add noahmchugh-stinkyboy-bodega -t streamable-http -u 'https://mcp.stinkyboy.co/mcp'
{
"mcpServers": {
"noahmchugh-stinkyboy-bodega": {
"type": "http",
"url": "https://mcp.stinkyboy.co/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.23 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 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.
- 25 Sept 26 +19
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 30
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 2 Oct 2026 · Probed https://mcp.stinkyboy.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=stinkyboy.co | CN=YE1,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6087bdcbb5b33a1352a7a64e8cb93caa8fb |
| SANs: *.stinkyboy.co, stinkyboy.co | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.stinkyboy.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| stinkyboy.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.stinkyboy.co/mcp | Unreachable | ||
| http (plaintext) | http://mcp.stinkyboy.co/mcp | HTTPS enforced |
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 →
call_tool ~33
Execute any catalog tool by id. Payment is charged on success only.
| Name | Type | Req | Description |
|---|---|---|---|
| inputs | – | – | – |
| tool_id | – | – | – |
No output schema declared.
No examples provided.
catalog_search ~49
Search all catalog tools. synthesize=true (default) compiles a missing tool on the spot instead of returning a miss.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | – | – | – |
| query | – | – | – |
| synthesize | – | – | – |
No output schema declared.
No examples provided.
create_and_call ~54
State the desired outcome with real inputs; the immediate compiler builds the missing tool and runs it in the same session.
| Name | Type | Req | Description |
|---|---|---|---|
| callback_url | – | – | – |
| inputs | – | – | – |
| outcome | – | – | – |
| path_hint | – | – | – |
No output schema declared.
No examples provided.
get_quote ~36
Price quote for a call or a build before commitment. Free, no payment needed.
| Name | Type | Req | Description |
|---|---|---|---|
| inputs | – | – | – |
| tool_id | – | – | – |
No output schema declared.
No examples provided.
my_spend ~27
Spend report for a caller wallet: calls, builds, receipts.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | – | – | – |
No output schema declared.
No examples provided.
tool_detail ~34
Full detail for one tool: price, schema, quality score, health, status, changelog.
| Name | Type | Req | Description |
|---|---|---|---|
| tool_id | – | – | – |
No output schema declared.
No examples provided.
What is the Stinkyboy Bodega MCP server?
Stinkyboy Bodega is an MCP server listed in the public MCP registry as io.github.noahmchugh/stinkyboy-bodega. One integration, one wallet. Thousands of callable tools, paid per call in USDC via x402. This page covers its hosted endpoint (https://mcp.stinkyboy.co/mcp).
Is the Stinkyboy Bodega MCP server safe to use?
Stinkyboy Bodega scores 52 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 Stinkyboy Bodega MCP server expose?
Stinkyboy Bodega exposes 6 tools: catalog_search, tool_detail, call_tool, get_quote, my_spend, create_and_call. Their descriptions and schemas cost roughly 233 tokens of context every time the server is loaded.
Does the Stinkyboy Bodega MCP server require authentication?
Its publisher declares no required credentials for Stinkyboy Bodega. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Stinkyboy Bodega MCP server still maintained?
Stinkyboy Bodega is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.