_ registry / mcp http-sse · checked 14h ago

testingapis

https://testingapis.com

Registry code: 5c7c2b225de6cae0

api record

Validate OpenAPI and JSON Schema, convert specs, curl to code, JSONPath, and free test data.

from a public catalogue that lists it, not from the operator

endpoint
https://testingapis.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is testingapis live?
Yes — it answered the hub's last check (checked 14h ago). It answered 100% of checks over the last 30 days.
Is testingapis free to use?
Yes — the hub reached it with no key and no payment.
What tools does testingapis have?
10 tools: get_test_data, validate_openapi, validate_json_schema, generate_json_schema, json_to_types, curl_to_code, convert_api_spec, query_jsonpath, ….
Is testingapis safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
231ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 10 tools
10 never probed 0 of 10 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_test_data unknown 14h ago

    Fetch realistic sample records from the free testingapis.com API to use as test data or fixtures: products (with prices, categories, ratings), blog posts or todos. Every record comes from a real, public REST endpoint the user can also call.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "resource"
      ],
      "properties": {
        "id": {
          "type": "integer",
          "maximum": 9007199254740991,
          "description": "One record by its id, instead of a list.",
          "exclusiveMinimum": 0
        },
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "How many records (5 by default)."
        },
        "resource": {
          "enum": [
            "products",
            "posts",
            "todos"
          ],
          "type": "string"
        }
      }
    }
    arguments 29 lines
  • validate_openapi unknown never probed

    Check an OpenAPI 3.0/3.1 or Swagger 2.0 document (JSON or YAML) for the mistakes that break tools: missing required fields, undeclared path parameters, invalid status codes, duplicate operationIds, broken $refs, undefined security schemes and examples that don't match their schema. Returns each problem with a JSON pointer and, for JSON, a line number.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "spec"
      ],
      "properties": {
        "spec": {
          "type": "string",
          "maxLength": 1000000,
          "description": "The whole OpenAPI or Swagger document, as JSON or YAML text."
        }
      }
    }
    arguments 14 lines
  • validate_json_schema unknown never probed

    Check a JSON document against a JSON Schema (drafts 4 to 2020-12, with $ref, allOf/anyOf/oneOf, if/then/else and formats). Returns every error with the JSONPath of the value and the keyword that failed.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "schema",
        "data"
      ],
      "properties": {
        "data": {
          "type": "string",
          "maxLength": 1000000,
          "description": "The JSON document to check, as JSON text."
        },
        "schema": {
          "type": "string",
          "maxLength": 1000000,
          "description": "The JSON Schema, as JSON text."
        }
      }
    }
    arguments 20 lines
  • generate_json_schema unknown 14h ago

    Create a JSON Schema (draft 2020-12) from a JSON sample. Every item in an array is read, so required, optional and nullable properties are worked out, and strings that are all dates, emails, URLs or UUIDs get a format.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "json"
      ],
      "properties": {
        "json": {
          "type": "string",
          "maxLength": 1000000,
          "description": "A JSON sample, such as an API response."
        },
        "strict": {
          "type": "boolean",
          "description": "Add additionalProperties: false to every object."
        }
      }
    }
    arguments 18 lines
  • json_to_types unknown never probed

    Generate types for a JSON sample in TypeScript, Go (with json tags), Python (Pydantic), Java (records with Jackson), C# (System.Text.Json), Kotlin (kotlinx.serialization) or Rust (serde). Optional and nullable fields are worked out from every item in arrays.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "json",
        "language"
      ],
      "properties": {
        "json": {
          "type": "string",
          "maxLength": 1000000,
          "description": "A JSON sample, such as an API response."
        },
        "language": {
          "enum": [
            "typescript",
            "go",
            "python",
            "java",
            "csharp",
            "kotlin",
            "rust"
          ],
          "type": "string"
        },
        "rootName": {
          "type": "string",
          "maxLength": 60,
          "description": "Name of the top-level type; Root by default."
        }
      }
    }
    arguments 32 lines
  • curl_to_code unknown 41h ago

    Turn a cURL command (bash, Windows cmd or PowerShell, as copied from browser devtools) into the same request in Python requests, JavaScript fetch or axios, Go, Java, C#, PHP, or a tidy cURL command. Headers, body, auth, timeouts and redirects are carried over.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "command",
        "language"
      ],
      "properties": {
        "command": {
          "type": "string",
          "maxLength": 1000000,
          "description": "The cURL command."
        },
        "language": {
          "enum": [
            "python",
            "fetch",
            "axios",
            "go",
            "java",
            "csharp",
            "php",
            "curl"
          ],
          "type": "string"
        }
      }
    }
    arguments 28 lines
  • convert_api_spec unknown 41h ago

    Convert between API description formats: OpenAPI 3, Swagger 2.0, a Postman collection, cURL commands or a HAR recording in; OpenAPI 3.1 (JSON or YAML), Swagger 2.0, a Postman collection v2.1, cURL commands or an .http file out. Anything the target format can't hold is listed.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "source",
        "to"
      ],
      "properties": {
        "to": {
          "enum": [
            "openapi-json",
            "openapi-yaml",
            "swagger-json",
            "postman",
            "curl",
            "http"
          ],
          "type": "string"
        },
        "source": {
          "type": "string",
          "maxLength": 1000000,
          "description": "The API description: OpenAPI or Swagger (JSON or YAML), a Postman collection, cURL commands or a HAR file."
        }
      }
    }
    arguments 26 lines
  • query_jsonpath unknown never probed

    Evaluate a JSONPath expression (RFC 9535: filters like $..book[[email protected] < 10], slices, recursive descent, length/count/match/search) against JSON. Returns each match with its normalized path.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "json",
        "path"
      ],
      "properties": {
        "json": {
          "type": "string",
          "maxLength": 1000000,
          "description": "The JSON to search."
        },
        "path": {
          "type": "string",
          "maxLength": 2000,
          "description": "The JSONPath, starting with $."
        }
      }
    }
    arguments 20 lines
  • explain_cron unknown 14h ago

    Read a cron expression (5 fields as in crontab, GitHub Actions and Kubernetes, or 6 with seconds as in Spring/Quartz, or @daily and the other shortcuts) in plain English, and list its next run times in UTC.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "expression"
      ],
      "properties": {
        "count": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "How many next run times to list (5 by default)."
        },
        "expression": {
          "type": "string",
          "maxLength": 200,
          "description": "The cron expression, such as */15 * * * *."
        }
      }
    }
    arguments 20 lines
  • compare_json unknown 41h ago

    List the differences between two JSON documents by their data, not their text: key order never counts, and array order can be ignored. Each difference has its JSONPath and both values.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "original",
        "changed"
      ],
      "properties": {
        "changed": {
          "type": "string",
          "maxLength": 1000000,
          "description": "The second JSON document."
        },
        "original": {
          "type": "string",
          "maxLength": 1000000,
          "description": "The first JSON document."
        },
        "ignoreArrayOrder": {
          "type": "boolean",
          "description": "Match array items by content instead of position."
        }
      }
    }
    arguments 24 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5c7c2b225de6cae0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5c7c2b225de6cae0/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/5c7c2b225de6cae0/badge.svg)](https://brick.blue/agent/5c7c2b225de6cae0?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.