Back to MCP servers

Normal Roughness Baker

https://server.smithery.ai/evozim-hv/normal-roughness-baker-mcp/mcp
● healthy

Normal Roughness Baker is an enterprise-grade Model Context Protocol (MCP) micro-service from the M2MCent network. Premium agentic endpoint for normal-roughness-baker-mcp. Monetized via x402 on Base Mainnet ($0.15 USDC per execution). Zero-gas settlement.

Transport
streamable-http
Auth
smithery_api_key
Cost
—
Protocol revision
2025-03-26
negotiated, not declared

MCP readiness

B · 79/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 83.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 10/10 initialize and tools/list both answered.
Live MCP endpoint 25/25 Endpoint answers the MCP initialize handshake (1153 ms).
Protocol revision 5/10 Speaks MCP 2025-03-26, 3 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 30/30 probes succeeded over 30 days (100%).
Tool declaration 5/10 Lists 1 tool(s) with descriptions.
Verified identity 5/10 Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags 4/5 seen in a source within 7 days.
Auth declaration 2/5 Declares credential scheme: smithery_api_key.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive (1153 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness
Higher than 40% of peers
This listing 79 · peer median 81
Latency
Faster than 48% of peers
This listing 340 ms · peer median 326 ms

Where it loses the most points, and how to win them back

  • Protocol revision −5 — Support the current protocol revision.
    Now: Speaks MCP 2025-03-26, 3 revision(s) behind 2026-07-28.
  • Tool declaration −5 — Declare every tool with a description and input schema.
    Now: Lists 1 tool(s) with descriptions.
  • Verified identity −5 — Claim the listing and prove control of its domain.
    Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

How to connect

MCP endpoint (streamable-http)
https://server.smithery.ai/evozim-hv/normal-roughness-baker-mcp/mcp
JSON-RPC initialize probe
curl -X POST https://server.smithery.ai/evozim-hv/normal-roughness-baker-mcp/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://api.m2mcent.com/normal-roughness-baker-mcp/api/process
Listed at (smithery)
https://api.m2mcent.com/normal-roughness-baker-mcp/api/process