Skip to main content
Glama
679,087 tools. Updated 2026-10-19 23:15

"How to implement intent recognition in MCP" matching MCP tools:

Matching MCP Servers

  • A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to search for products and prepare carts under a self-hosted, developer-controlled policy, with every purchase requiring a passkey-signed human approval before payment on the merchant's checkout.
    3
    Apache 2.0

Matching MCP Connectors

  • AudD MCP is a way for agents to add music recognition to apps or to fulfill song identification requests. It connects you to AudD, the music recognition API

  • Token intent checks; no simulation/signing. Free trial ends 2026-09-25. No NFT required.

  • Export workspace context as CLAUDE.md, cursorrules, or intent-md files. Choose format and optionally specify an intent or product ID.
    MIT
  • Preview SQL queries to assess safety, intent, and cost before execution, with automatic LIMIT applied.
    AGPL 3.0
  • Create a structured intent spec by providing a title, objective, and product ID. Use with list_intents to avoid duplicates.
    MIT
  • Check your daily recognition credit balance to track available SPINES credits before searching books or managing reading lists.
    MIT
  • Retrieve a paginated list of async jobs for invoice generation, revenue recognition, and other background processes.
    MIT
  • Retrieve a numeric Sorsa Score to estimate the recognition and influence of an X/Twitter account. Provide the handle, user ID, or profile URL.
    MIT
  • Save a structured intent spec to intent.md after building it through conversation. Define objectives, outcomes, constraints, and edge cases.
    MIT
  • Modify an unconfirmed payment intent to adjust amount, currency, metadata, or payment settings before confirmation in OrcaRail crypto payments.
    MIT