Loading ToolBench

Reading the current corpus…

oblique-examples MCP server · F · ToolBench

← Browse

oblique-examples

github.com/oblique-markets/oblique-examples

Example implementations of x402 payment-enabled tools and MCP servers for the oblique.markets API

2026-07-28+STREAMABLE_HTTP2 tools

35/100

Definition Quality35

Protocol Readiness25

Supportability43

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence · evidence: Streamable HTTP

Current-spec patterns detected

Summary

This is an examples repository, not an MCP server. The two tools (bazaar_pulse, bazaarPulse) are LangChain and Vercel AI SDK implementations, not MCP tool definitions. No MCP server code is present, only configuration examples (mcp.json) pointing to remote servers. The tools have good descriptions (120-140 chars, within baseline 194 avg) but zero input schema visibility in the source. Tool definitions are inferred from framework code, not explicitly registered as MCP tools.

Tools (2)

bazaarPulseread onlyauth35/100

Get today's x402 Bazaar market pulse: which paid API listings were added, removed or repriced in the last day, plus catalogue totals. Costs $0.002 USDC per call. Use for questions about what is new or moving in the x402 economy.

bazaar_pulseread onlyauthsource verified35/100

Get today's x402 Bazaar market pulse: which paid API listings were added, removed or repriced in the last day, plus catalogue totals. Costs $0.002 USDC per call. Use it to answer questions about what is new or changing in the x402 economy.

Issues (5)

CRITICALtool ↗

No MCP server implementation present. Repository contains only LangChain/Vercel AI SDK examples and remote server configuration. Tools are not registered as MCP tools.

bazaar_pulsebazaarPulse

CRITICALconstrained-input ↗

Input schemas completely absent. Both tools accept empty input {} but no JSON Schema definition is visible in source code.

bazaar_pulsebazaarPulse

HIGHresponse-shaper ↗

No output schema documented. Tools return JSON responses but structure is not formally defined for LLM consumption.

bazaar_pulsebazaarPulse

HIGHtool ↗

Tool definitions inferred from framework code, not explicitly registered.

bazaar_pulsebazaarPulse

HIGHrecovery-guide ↗

Recommendations

Create an actual MCP server implementation (e.g., using mcp-sdk-python or mcp-sdk-typescript) that registers bazaar_pulse as an MCP tool with explicit JSON Schema input/output definitions.
Add formal JSON Schema for tool inputs (even if empty, declare it as {"type": "object", "properties": {}, "required": []}) and outputs (document the Bazaar pulse response structure: fields, types, pagination if any).
Document output schema in tool description: 'Returns object with fields: listings_added (array), listings_removed (array), listings_repriced (array), total_listings (number)', or actual structure.
Add error handling guidance: 'If payment fails, check wallet balance on Base. If endpoint times out, retry after 30s. If HTTP 402 returned, x402 payment challenge failed, verify PRIVATE_KEY and USDC balance.'
Split examples into separate directories: /mcp-server (actual MCP implementation), /integrations (LangChain/Vercel examples). Make it clear which is the canonical MCP server.

Score history

Overall score trend

First recorded score · v2 rubric

35/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	35	2026-07-28+	v2