Calendar App MCP

An MCP service designed for deploying HTML content to EdgeOne Pages and obtaining an accessible public URL.

Real-time crypto data for AI assistants. Live price spreads between Binance and OKX, perpetual funding rates, Cash & Carry arbitrage yields, and exchange status. No API key required.

Revuo is the B2B SaaS directory built for the AI-citation era. While G2 and Capterra were built for humans clicking through review pages, Revuo is built for the parallel reality where buyers' first stop is an LLM. Every listing carries a typed capability schema (integrations, standards support, pricing model, deployment options), is continuously re-verified by a weekly crawler, and is exposed via a public MCP server agents can call directly. Revuo's three launch verticals are PIM/PXM, Tender Management, and Billing & Invoicing — chosen for ACVs that justify vendor distribution spend and for AI-citation buyer behavior that already exists today. Capability-structured. Continuously verified. Agent-callable.

One API for Search, Crawling, and Sitemaps

Search, rank, and compare 500K+ AI models, datasets, papers from 13+ platforms. Hardware-aware model selection with VRAM/license constraints. FNI-scored rankings with full factor breakdown.

Deploy static sites on Hostsmith - give it a file, get a live HTTPS URL. EU/US residency.

MCP server for querying Janus analytics — let your AI agent check your dashboard, events, funnels, and usage.

A Model Context Protocol (MCP) server for image generation and manipulation using fal.ai's Stable Diffusion model.

Real-time prediction market + Hyperliquid perps intelligence for Claude. 22 tools combining Polymarket, HIP-4 on-chain markets, and Hyperliquid perpetuals — cross-platform signals, funding outliers, OI caps, liquidation clusters, whale activity, and HIP-4 vs Polymarket arb. Free tier (100 calls/day, no email required).

MCP wrapper for Askew's x402 endpoints — 8 tools (3 free, 5 paid in USDC on Base): live DeFi yield comparison, SOL/ATOM staking routing, agent-economy research search, Guardian security threat intel, and a combined strategic feed.

The match graph for AI. Search 100,000+ capabilities across 13,000+ AI artifacts — models, agents, MCP servers, APIs, frameworks, CLIs, and more. Every query learns from the graph, making the next search smarter. 10 tools: search, find_mcps, get_artifact, compare, find_stack, resolve_capability, trust_passport, feedback, subscribe, unsubscribe. Install: npx -y @unfragile/mcp-server

高德地图官方 MCP Server

Open-source MCP memory server for AI agents — persistent, searchable, tiered memory across sessions. Works over stdio (Cursor, Claude Desktop) or HTTP+SSE. MIT licensed (separate commercial license available).

Retrieving and analyzing issues from Sentry.io

The first payment-contingent FX protection server on MCP. Price a Guard (invoice-linked FX protection for SME invoices and payables), get live spot and forward rates, model 25 years of historic FX stress scenarios, and resolve settlement dates — all via natural conversation. Public endpoint, no authentication required. Designed for PSPs, accounting platforms, and agentic cross-border payment workflows.

staffSign MCP Server — Digital employment contracts for HR and staffing agencies. Create, send, and track e-signatures via AI agents. 12 tools including QES (eIDAS) support. Pay-per-use, no subscription. Built for the DACH market, EU-compliant.

Verify AI agent tool calls with content-addressed, HMAC-attested receipts. Free third-party verification API for AI agents. Call verify_action(claim, evidence) to get an independent integrity check on whether your claimed action matches the actual evidence. Useful for catching silent failures: incorrect SQL operations, file-op mismatches, API call inconsistencies, and code-diff scope creep. Five specialized verifier kinds: - code_diff: verb / path / identifier coherence with unified diff - db_op: row delta + SQL operation + ID match - file_op: existence state + line/size delta - api_call: request body and response status coherence - generic: conservative fallback Returns: - aar_verdict: verified | contradicted | insufficient_evidence | unsafe_to_verify - verdict: ok | mismatch | uncertain (legacy 3-value alias) - reasoning, confidence - receipt: verify_action_receipt.v0 with HMAC-SHA256 signature, content-addressed via SHA-256 hashes of claim and evidence Cross-vendor: works with Claude Code, Cursor, Cline, Codex, Codeium, and any MCP-compatible harness. Stateless, per-request, no API key, no registration. Pure Python stdlib (no pip install). Anonymized telemetry only — no PII, no model fingerprint, no raw claim/evidence retention. Honest scope: this is a small reference implementation, not a canonical inter-vendor standard. v0 receipts use HMAC-SHA256 (symmetric, single-issuer); v1 with ed25519 + multi-issuer is on the roadmap. The hosted endpoint has no SLA — self-host for stability (git clone && ./start.sh). 90-day probe with explicit kill criteria. If adoption appears, v1 schema work begins. If response is null, the null is itself a publishable data point.

Zhipu Web Search MCP Server is a search engine specifically designed for large models. It integrates four search engines, allowing users to flexibly compare and switch between them. Building upon the web crawling and ranking capabilities of traditional search engines, it enhances intent recognition capabilities, returning results more suitable for large model processing (such as webpage titles, URLs, summaries, site names, site icons, etc.). This helps AI applications achieve "dynamic knowledge acquisition" and "precise scenario adaptation" capabilities.

An MCP server and REST API that classifies Polymarket wallets as human or bot, scores their trading edge from 0–10, and streams their current open positions. Built for AI agents on copy-trading and signal-following stacks. # Use it from any MCP client (Claude Desktop, Cursor, etc.) pip install polymarket-intel-mcp polymarket-intel-mcp # Or call the hosted REST API directly curl https://polymarket-intel-production.up.railway.app/wallet/0xf1528f12e645462c344799b62b1b421a6a4c64aa How this fits with other Polymarket MCP servers There are several MCP servers covering Polymarket, each at a different layer: Server What it does When to use it polymarket-intel (this) Wallet intelligence — classify human vs bot, score trading edge, read open positions Deciding whose signals to follow graph-polymarket-mcp Market data via The Graph subgraphs (20 tools, 8 subgraphs) Reading raw on-chain market data whitmorelabs/polymarket-mcp Slippage, liquidity, arbitrage, price feeds Pricing your own trades joinQuantish/polymarket Self-hosted trading agent Running an autonomous bot These complement each other. A copy-trading agent would use polymarket-intel to filter wallets worth following, then graph-polymarket-mcp to read the markets those wallets are betting on, then whitmorelabs/polymarket-mcp to size its own entries. What it answers "Is this trader a human or a bot?" — score_polymarket_wallet(wallet_address) → returns classification ∈ {human, bot, insufficient_data} plus a confidence score and reason codes. "Do they actually have an edge?" — edge_score from 0–10, gated on net realised PnL so distributed-but-losing wallets don't get false positives. "What are they betting on right now?" — get_open_positions(wallet_address) returns live positions sorted by size, refreshed every 30s. "How has their edge changed over time?" — /wallet/{address}/history returns the score time series from the daily snapshots. Why this exists The Polymarket leaderboard is misleading. It includes unrealised PnL marked-to-current-price, so the names at the top are dominated by bots running structural arb plus a few wallets sitting on huge open positions that may never resolve in their favour. Agents that copy-trade naively from the leaderboard get burned. This service runs every leaderboard wallet through behavioural fingerprinting (focus ratio, holding period, timing regularity, category concentration) plus PnL reconstruction from raw activity, and only surfaces traders that look like genuine humans with a real edge. The dataset grows more valuable over time — every day the snapshot job runs, historical signals accumulate. Wallets that have been consistently above edge 7 for 90 days are a stronger signal than any single point-in-time score. Distributed as both a REST API and an MCP server Surface Use case Setup MCP server Agent that needs tool-style access pip install polymarket-intel-mcp REST API Custom HTTP integration, dashboards curl https://polymarket-intel-production.up.railway.app/... Hosted MCP Agent on any MCP-compatible client Add https://polymarket-intel-production.up.railway.app/mcp to client config Architecture ┌──────────────────────────────────────────────┐ │ core/ │ │ client.py — Polymarket data API client │ │ signals.py — pure signal calculators │ │ scorer.py — classifier + edge score │ │ models.py — Pydantic response schemas │ ├──────────────────────────────────────────────┤ │ db/ │ │ schema.sql — Postgres tables + indexes │ │ repository.py — Repository protocol + │ │ InMemoryRepository │ │ supabase_repo.py — Supabase impl │ │ converters.py — ScoreResult ↔ records │ ├──────────────────────────────────────────────┤ │ api/main.py — FastAPI HTTP server │ │ mcp_server/ — MCP server (stdio) │ │ scripts/ │ │ analyze_wallet.py — CLI │ │ snapshot_job.py — daily cron entry │ │ tests/ │ └──────────────────────────────────────────────┘ Core has no idea persistence exists. The API and snapshot job depend on the Repository protocol — Supabase in production, in-memory in tests and when env vars are unset. This is what makes the suite run without a database and what lets you swap Supabase for Neon, RDS, or anything else later by adding one file.

Model Context Protocol server for the Lacuna Music API — generate AI music from Claude Desktop, Claude Code, Cursor, Zed, and other MCP-compatible clients.

Web content fetching and conversion for efficient LLM usage

Render music notation from a JSON score to inline SVG (Verovio + Bravura), round-trippable MusicXML, and base64 MIDI in one call. Includes pre-flight validation with concrete fix suggestions and a curated music-theory knowledge search. Free, open, no auth, sponsored by Gradus School of Music Composition.

staffSign MCP Server — Digital employment contracts for HR and staffing agencies. Create, send, and track e-signatures via AI agents. 12 tools including QES (eIDAS) support. Pay-per-use, no subscription. Built for the DACH market, EU-compliant.

MCP Advisor & Installation - Use the right MCP server for your needs

terminal-history-mcp gives AI agents (Claude Code, Cursor, Cline, Zed, any MCP client) full-text search over your shell history. - Local-only, no cloud — SQLite FTS5 at ~/.terminal-history-mcp/history.db - Supports zsh, bash, fish - Captures cwd, exit code, duration via opt-in shell hook - 11-pattern secret redaction runs BEFORE insert (GitHub PATs, OpenAI keys, AWS, JWTs, bearer tokens, env vars, CLI flags, basic-auth URLs) - Hash-deduped, idempotent reindex - WAL mode — safe across parallel sessions Ask: "When did I last ssh into staging?", "Show failed commands today", "What did I run in /etc/nginx yesterday?", "Show context around kubectl apply".

The Milvus MCP server enables AI applications to interact with Milvus vector databases using natural language commands. It allows AI models to perform vector searches, manage collections, and retrieve data without writing custom database queries. This integration facilitates seamless access to vector data, enhancing the capabilities of AI tools like Claude Desktop and Cursor.

GBOX provides environments for AI Agents to operate computer and mobile devices. Mobile Scenario: Your agents can use GBOX to develop/test android apps, or run apps on the Android to complete various tasks(mobile automation). Desktop Scenario: Your agents can use GBOX to operate desktop apps such as browser, terminal, VSCode, etc(desktop automation). MCP: You can also plug GBOX MCP to any Agent you like, such as Cursor, Claude Code. These agents will instantly get the ability to operate computer and mobile devices.