Skip to main content
Glama
21,689 servers. Updated

"Information about the programming language Rust" matching MCP connectors:

GET /v1/connectors – MCP directory API reference

Matching Connector Tools:

  • Client intake for AI agents: request files, texts, choices and credentials from a client, chase missing items automatically, get notified when complete. Hosted Streamable HTTP endpoint with OAuth 2.1 (PKCE, dynamic client registration); the same tools as the @briefgate/mcp npm package.

  • Brazilian foreign trade, crop and commodity data as a remote MCP server. Exports and imports from MDIC/ComexStat since 2000, by HS code (SH4/SH6/NCM) and partner country, in USD FOB and kilograms — plus crop production, supply-and-demand balances, climate readings and production forecasts for hubs such as soybean, coffee, corn, beef and cocoa. Every comparison is like-for-like: two windows of equal length, each labelled with the period it actually measures, and every answer names its window and its source. 15 read-only tools, metered in credits. Nothing to install: Streamable HTTP at https://mcp.kyrodata.com/mcp with a bearer key or OAuth 2.1 (PKCE). Official registry: com.kyrodata/kyrodata.

  • Non-custodial Hyperliquid perpetual-futures trading for Claude, Cursor and any MCP client: live market data, orderbook, candles, account state and — once the user arms it — order execution with on-chain leverage on the user's own wallet. No withdraw tool, server-enforced caps.

  • Yelp business search, place details and the full review feed, as structured JSON.

  • The public product catalogue and collections of any Shopify storefront, as structured JSON.

  • Publish in seconds, get the audience, start monetization, get all analytics — without leaving your agent. Playgama MCP is a remote MCP server for game developers. Point Codex, Claude Code, Cursor or VS Code at it and your agent works inside your Playgama developer cabinet: it creates a game and fills in the form, uploads a build and polls until the engine analysis is done, uploads covers in the exact sizes the form requires, edits the in-app catalog and leaderboards, gets a QA Tool link, and publishes a sandbox — a public link anyone can play, with no moderation step. It can also bring the first players to that sandbox through Playgama DSP, with the first run per game free. 22 tools, 11 of them read-only; every write is annotated as destructive so your client asks first. Submitting to moderation, deleting and payouts are deliberately left out: the agent prepares everything, a human presses the button. Authentication is OAuth 2.1 with dynamic client registration — there is no token to copy. The client opens a browser on first use, and connected agents are listed and revocable in the cabinet. After the link is live the game takes its first players from the Playgama network, and Playgama DSP can send more the same day (beta). Once it clears the session threshold you can switch on advertising — Playgama Ad serves rewarded, interstitial and banner formats through one JS SDK (access by request). Playgama Wrap turns the same game into a standalone site on your own domain with player accounts, in-game purchases and indexable SEO pages (early access), and Playgama Bridge SDK gives one API for ads, leaderboards, payments and platform SDKs when you publish across platforms. Playtime, retention and revenue reports are in the developer dashboard, and payouts start at 100 USD. Product page: https://playgama.com/mcp/ Docs: https://wiki.playgama.com/playgama/mcp Tools reference: https://wiki.playgama.com/playgama/mcp/tools Connected agents: https://developer.playgama.com/mcp

  • **Can AI actually read your page?** ChatGPT, Perplexity, Claude and Google's AI Overviews fetch pages very differently from your browser — no JavaScript, tight timeouts, and a robots.txt rulebook of their own. Lekta fetches a URL exactly the way they do and grades what survives, **A+ to F**. This is the technical half of **AEO** (answer engine optimization) and **GEO** (generative engine optimization): before a model can cite you, it has to be able to fetch you, parse you, and find one sentence worth quoting. **The loop this server was built for:** `Audit https://mysite.com/pricing with Lekta, apply the fixes it lists, audit it again, and show me the difference.` Your agent gets a graded verdict, a ranked fix plan with the exact markup to paste, and a diff that proves the change landed. Repeat until A+. **Four layers, 100 points:** **Access** 25 — do the ~17 AI crawler tokens get past robots.txt? **Indexability** 25 — how much content survives without JavaScript? **Answerability** 30 — is there a single quotable sentence an engine can lift? **Recency** 20 — can a model tell when this page was last true? **What this is not:** a rank tracker. Lekta will not tell you how often ChatGPT mentions your brand. It tells you whether your page can be read and quoted when it does — the part you can actually fix. **No black box.** Every finding cites its basis — an RFC, a vendor doc, or a dated measurement we ran. The engine is versioned with a public changelog: a score never moves without a published shift table. **Tools:** `lekta_audit` (fresh fetch) · `lekta_report` (cached read) · `lekta_fix_plan` (ranked, paste-ready) · `lekta_diff` (before/after) · `lekta_my_sites` Listing tools is open. Tool calls need a free key from lekta.dev/en/panel/api — send `Authorization: Bearer lekta_…` or `x-api-key`. Cached reads, fix plans and diffs cost nothing; only fresh fetches count against the daily limit. **Topics:** AEO · GEO · AI SEO · LLM SEO · answer engine optimization · generative engine optimization · AI crawler access (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) · JavaScript-free indexability · structured data · content freshness

  • Give your agents your team's real data — read the shared graph, propose actions your team approves.

  • Bing search results with the ad block and Copilot answer, geo and market targeting, as JSON.

  • Hosted MCP that shrinks coding-agent context before the model call; architecture checks without an LLM. Zero data retention.

  • MCP facade over the Nebelus Construction API. ~48 tools give full agent build parity: create/update/probe agents, edit graphs, attach knowledge and vector stores, wire connectors, set governance policies and locked guardrails, enable grounding-trace, and read deployment wiring. Purpose-built for regulated industries: data residency is enforced per region (EU / GCC-KSA), with PII controls and an audit trail. Agents are created as drafts — no deploy tool is exposed over MCP by design; publishing happens in the Nebelus console.

  • Send and receive faxes from any MCP-compatible AI assistant using the Fax.Plus API

  • The official Model Context Protocol (MCP) server for RubiConnect — the enterprise platform for RCS (Rich Communication Services) and WhatsApp Business messaging. Connect external AI assistants (such as Claude Desktop, Claude.ai, Cursor, ChatGPT, and autonomous agent pipelines) directly to your RubiConnect messaging workspace to check phone reachability, send rich cards and carousels, trigger bulk campaigns, inspect live inbox conversations, and query messaging analytics.

  • IPStack MCP Adapter turns IPStack's REST APIs into Model Context Protocol tools so any MCP-compatible client can call them directly in conversation. The first release ships IPStack IP geolocation and security lookups (single IP, caller's IP, and bulk). Additional APILayer services are added by registering them in a single config file, so the catalog grows without client-side changes.

  • The PostNitro MCP server lets AI assistants and agents — Claude (Desktop, Code, and Cowork), Cursor, ChatGPT, and any other Model Context Protocol client — create carousels, image posts, and videos, manage brand kits, audio tracks, and connected social accounts, and schedule posts directly. Instead of writing REST API calls, you connect the server once and your AI assistant gets ready-made tools covering carousel, image, and video generation, brands, audio, social accounts, and scheduling.

  • OutSend is a B2B prospecting platform exposed as a remote MCP server. Ask your assistant for "1,000 plumbers in Lyon with verified emails" and it runs the whole job on OutSend: extract local businesses by search query and geographic area with a cost and volume estimate before launching, enrich any finished job with emails, social profiles, reviews, tech stack, and email deliverability checks, chain steps into pipelines (extract, enrich, filter, verify) and schedule recurring monitors that rerun

  • Screen 2,400+ NSE equities with the Sift query language over 30 years of daily data.

  • API documentation drifts away from the running service, so consumers integrate against a contract nobody keeps. Routebase keeps API design, testing, mocking and documentation on one living source of truth, and this MCP server exposes that workspace to AI agents. Agents can design endpoints, write and run test suites, manage mock servers and publish documentation, always under the permissions of the connected Routebase account.

  • Fixter's MCP provides a stream-lined agentic way to onboard, setup and use the Fixter monitoring and observability platform. Check out more at https://fixter.dev/

  • Connect Claude, Cursor, and other MCP-compatible coding agents to DevTune AI search visibility data with the Streamable HTTP Model Context Protocol server. DevTune exposes a Model Context Protocol (MCP) server so that AI agents can query your AI search visibility data directly. This lets agents like Codex, Claude, Cursor, and other MCP-compatible tools access your metrics and data directly.