掌锤公开查询 MCP
Related Servers
Alternatives to 掌锤公开查询 MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceExposes read-only tools for searching players, fetching profiles, live matches, match history, stats, leaderboards, heroes, team-ups, insights, matches, and factions from Marvel Rivals public data. It also returns an MCP-UI player dashboard rendering rank, competitive record, live match rosters, hero win rates, and recent match form, over local stdio or Streamable HTTP.192 PyPI1MIT
- AlicenseAqualityBmaintenanceProvides read-only Arknights intelligence over MCP, enabling structured queries about stages, enemies, operators, and modules with region tagging and evidence-backed analysis. It uses versioned SQLite snapshots and never fetches upstream data at query time.413Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables read-only access to BuzzerBeater's public API through MCP tools for retrieving team, player, match, market, national team, and other game data.MIT
- AlicenseAqualityCmaintenanceA read-only MCP server for AppDynamics that exposes 12 task-oriented tools to query applications, topology, metrics, snapshots, health rules, anomalies, events, alerting config, analytics events, and dependency maps via OAuth API-client credentials.121MIT
- AlicenseAqualityAmaintenanceEnables read-only access to Google Analytics 4 data through seventeen tools covering reports, realtime data, funnels, pivots, metadata, and admin lists. It runs locally with service account credentials and lets users query properties via standard MCP clients.1742 PyPIMIT
- AlicenseBqualityCmaintenanceEnables MCP clients to inspect and operate SQLite, PostgreSQL, MySQL/MariaDB, Oracle, SQL Server and MongoDB through 16 tools covering schema discovery, parameterized SQL reads and transactions, MongoDB document operations, and concurrent hybrid SQL/MongoDB queries. Runs locally over stdio or loopback HTTP with pooled connections, bounded concurrency, row and response limits, and read-only defaults.16MIT
TDQS
Scored across 8 tools
The tools mostly target distinct resources: reports, rosters, matchups, and dataset artifacts. The only mild overlap is between get_report and the dataset tools (get_dataset_manifest/get_dataset_rows), but descriptions distinguish report reading from raw dataset pagination.
All tools follow a consistent verb_noun snake_case pattern: list_reports, get_report, get_matchups, list_rosters, get_roster, get_data_notes, get_dataset_manifest, get_dataset_rows. No mixed casing or vague verb styles.
Eight tools is well-scoped for a public query server covering reports, rosters, matchups, and datasets. Each tool appears to earn its place without obvious redundancy.
The surface covers listing and retrieving reports, rosters, matchups, and dataset pages, with guidance notes and manifests. Minor gaps may exist around broader search/filtering, but the core read-only public query workflows are covered.