Skip to main content
Glama
gerefull

InvokePort — JSON Schema Validation, JSON to TypeScript, CSV to JSON, JSON Repair & JSON to CSV

Related Servers

Alternatives to InvokePort — JSON Schema Validation, JSON to TypeScript, CSV to JSON, JSON Repair & JSON to CSV

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Portable agent tools with typed schemas (diff, cron, units, JSON→TS, outdoor helpers, prompts). Free to try—no account required.
      30
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to check requests against a live OpenAPI 3.x specification rather than guessing, by resolving endpoints from a docs anchor, operationId, path fragment or tag, revealing what each operation accepts and returns with $refs resolved, and diffing a concrete payload to report missing, unknown, mistyped, or forbidden fields with suggested corrections. All five tools are strictly read-only, never touching the API the schema describes, and return actionable errors with close-match suggestions.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      72 free, open-source (MIT) developer tools over a stateless, no-key MCP server: JSON/YAML/CSV conversion, PDF and image processing, JWT/hash/UUID utilities, DNS/TLS/HTTP checks, llms.txt and AI SEO checks, and more. Streamable HTTP with JSON responses.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to call 16 small, deterministic, read-only tools over a free, no-auth remote streamable HTTP MCP endpoint, covering business idea scoring, price headroom, hotel OTA commissions, open-source SaaS swaps, ads policy notice risk, App Store 4.2 prechecks, and Japan trip planning. Each tool is also exposed as a plain JSON API with OpenAPI docs.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to discover services and check API contracts via tools like directory search, API Doctor, and receipt verification, without requiring an account or payment.
      MIT

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools serve distinct roles in a clear workflow: search_capabilities finds available capabilities, get_capability retrieves their schemas/examples, and invoke_capability executes them. There is no overlap in purpose, and an agent can easily tell which tool to use at each step.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (search_capabilities, get_capability, invoke_capability). The minor pluralization difference in 'search_capabilities' does not break the pattern.

    Tool Count5/5

    Three tools are well-scoped for a capability hub: they cover discovery, inspection, and execution without redundancy. The count is at the low end of the typical 3–15 range but is appropriate given the data-driven design where many capabilities share the same interface.

    Completeness5/5

    The surface covers the full lifecycle of a capability hub: search for capabilities, get their schemas and examples, and invoke them. No obvious gaps exist for the stated domain of JSON/data transformation capabilities, and agents can complete any advertised task end-to-end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues