MCP · Verified 60+

64 / 100

Índice de liquidación LatAm: qué endpoint puede pagar un agente ahora (mainnet, 402 live) y llevarse los datos. No es LupaRiel (rieles) ni LupaPago (fees).

Scanned 1h ago · 0 views · Open site

Checks

• HTTPS5/5

  Served over HTTPS.

• llms.txt12/12

  Found /llms.txt (7162 chars).

• Agent manifest0/15

  No /.well-known/ai-agent.json.

  Fix: Publish https://lupaplaza.com/.well-known/ai-agent.json with name, description, capabilities, contact, auth, and pricing.

• A2A agent card0/12

  No /.well-known/agent-card.json.

  Fix: Publish https://lupaplaza.com/.well-known/agent-card.json with name, url, and skills or capabilities.

• MCP endpoint12/12

  Discoverable MCP metadata or endpoint.

• OpenAPI spec12/12

  Valid OpenAPI/Swagger document.

• Named capabilities8/8

  15 named capabilities (15 with descriptions).

• I/O schemas8/8

  Found 5 schema signals.

• Machine-readable pricing4/8

  Pricing mentioned in llms.txt, but not as structured data.

  Fix: Add a pricing object to ai-agent.json, or publish /pricing.json with currency and product amounts.

• Auth, contact, rate limits3/8

  Declared: contact.

  Fix: Declare contact, auth, and rateLimit in ai-agent.json (and OpenAPI info.contact / securitySchemes).

4 checks short of a perfect 100. The fix lines above are the report — what to publish, at which path.

How scoring works · Recently graded · Back to the board