Skip to main content
Glama
Verfi-io

verfi-mcp-server

Official
by Verfi-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to verfi-mcp-server

No user-submitted related servers found.

    Related Servers

    • joltsms-mcp-server

      rchanllc
      A
      license
      A
      quality
      C
      maintenance
      MCP server for provisioning dedicated real-SIM US phone numbers, receiving inbound SMS, and extracting OTP codes. Built for AI agents automating phone verification workflows.
      12
      258 npm
      1
      MIT

    • voygr-mcp

      VaarunSinha
      A
      license
      A
      quality
      B
      maintenance
      MCP server for VOYGR place verification and outbound venue calls. It provides tools to verify places, make structured calls, check credits, and access call transcripts/events.
      7
      1
      MIT
    • teta-pi by teta-pi

      teta-piofficial

      teta-pi
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the TETA+PI verified entity registry, enabling AI agents to search, verify, and route intents to trusted entities.
      1
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have distinct purposes: search/lookup, proof retrieval, consent verification, claim lifecycle, listing, expiration update, and SDK setup. There is some conceptual overlap among verfi_search_session, verfi_get_proof, and verfi_verify_consent because all involve retrieving or evaluating session/consent data, but descriptions clarify their different outputs and use cases.

    Naming Consistency5/5

    All tools use a consistent verfi_ prefix followed by a snake_case verb_noun pattern. Names are predictable and easy to scan, with only natural variations like get_claim_status and add_sdk.

    Tool Count5/5

    Nine tools is well-scoped for a consent/session management server. Each tool covers a distinct operation in the claim and verification workflow, with no obvious filler tools.

    Completeness4/5

    The surface covers session lookup, consent verification, proof retrieval, claim/unclaim, listing, expiration updates, and SDK setup, which is strong lifecycle coverage. Minor gaps may exist around explicit consent revocation or session creation, but those appear to be handled outside the MCP server via the SDK or platform.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources