MCP Queen Registryofficial
A
licenseA
qualityA
maintenanceCrawls and grades MCP servers deterministically, providing a registry, leaderboard, and API to query server grades and submit feedback.
Last updated
7
MIT
fresh-feeds — trending/new/changed MCP servers + x402 change-data API
Server Details
Trending/new/changed MCP servers: a liveness-probed freshness index + x402-paid change-data API
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- foomworks/fresh-feeds
- GitHub Stars
- 0
- Server Listing
- fresh-feeds
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.9/5.0
Tool DescriptionsA
Average 4/5 across 9 of 9 tools scored. Lowest: 3.3/5.
Server CoherenceA
Disambiguation5/5
Each tool has a clearly distinct purpose: feeds_status for overall freshness, registry-specific tools (snapshot, changes, highlights, search) and x402-specific tools (snapshot, list) are separated, and verification tools are distinct in scope (preview vs full). Descriptions explicitly clarify differences between free and paid versions.
Naming Consistency3/5
Tool names mix conventions: some start with 'get_', others with 'list_', 'search_', 'verify_', and 'feeds_status' uses noun_verb without a prefix. While readable, there is no uniform verb_noun pattern across all tools.
Tool Count5/5
With 9 tools, the server covers its domain concisely without being bloated. Each tool serves a clear function, and the count is well within the ideal 3-15 range.
Completeness4/5
The tool set covers core operations for the MCP registry and x402 services: search, browse highlights, get changes, verify servers, and retrieve full snapshots. Minor gaps exist (e.g., getting a single server's full registry info beyond search results), but these do not significantly hinder typical workflows.
Available Tools
10 toolsassess_agent_riskInspect
Verify-before-you-pay: a read-only fraud/impersonation RISK assessment (0-100, higher = riskier) for an ERC-8004 agent on Base, cross-referencing its DECLARED identity (agent-card) against on-chain control (ownerOf). Flags owner-mismatch, registration-inconsistency, off-chain/unproven cards, dead endpoints, and orphaned identities. Free; from a maintained sample of the first agentIds. Look up by tokenId (agentId) OR by the counterparty wallet/payTo you're about to pay (address — 0x… or eip155:8453:0x…). Omit both to list the sample (riskiest first).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| address | No | the wallet/payTo you're about to transact with (0x… or CAIP-10 eip155:8453:0x…); resolves to the matching agent(s)' risk in the sample | |
| agentId | No | ERC-8004 Identity tokenId on Base; omit to list the maintained sample |
feeds_statusInspect
Freshness/health of both feeds (snapshot ages, counts, available change-baseline dates). Free.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_mcp_registry_snapshotInspect
PAID (x402): returns x402 payment instructions for the FULL deduped, quality-scored MCP registry snapshot. Use search_mcp_registry (free) for targeted lookups.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_registry_changesInspect
PAID (x402): returns x402 payment instructions for the registry delta (added/removed/changed servers) since a daily baseline — the cheap habit endpoint for repeat callers.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| since | No | baseline date YYYY-MM-DD (see feeds_status for available dates) |
get_registry_highlightsInspect
Top 10 MCP servers by quality score + trending (new arrivals / score risers) + snapshot freshness. Free.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_x402_services_snapshotInspect
PAID (x402): returns x402 payment instructions for the FULL liveness-probed x402 services feed.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_x402_servicesInspect
List the x402 services discovery catalog's active edge, liveness-probed: know a service is up and correctly demanding payment before you pay it. Free; up to 25. For the full liveness-probed feed use get_x402_services_snapshot (paid, x402).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | max results 1-25 (default 10) | |
| payable_only | No | only services currently returning 402 (payable right now) |
search_mcp_registryInspect
Search the continuously-maintained MCP server registry (deduped, quality-scored, refreshed every 30 min) by name/title/description. Free; returns up to 25 matching servers with score, status, remotes and packages. For the FULL corpus (~1500 servers) use get_mcp_registry_snapshot (paid, x402).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | max results 1-25 (default 10) | |
| query | No | case-insensitive substring matched against server name/title/description; omit for the top servers by quality score |
verify_mcp_serverInspect
Free preview-grade trust report for one registry MCP server: a transparent 0-100 grade from cached signals (registry status, endpoint presence, freshness). The full report with a LIVE endpoint reachability probe + component breakdown is paid (verify_mcp_server_report, x402).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| server | Yes | MCP registry server name (use search_mcp_registry to find one) |
verify_mcp_server_reportInspect
PAID (x402): returns x402 payment instructions for the FULL verification report (LIVE endpoint probe + component breakdown) for one registry MCP server.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| server | Yes | MCP registry server name |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseCqualityCmaintenanceEasily find MCP servers using our MCP registry. Search with natural language.Last updated15MIT
- Flicense-qualityBmaintenanceMCP server providing live Wikipedia recent changes feed, page summaries, trending pages, and Wikidata entity lookup.Last updated
- Flicense-qualityCmaintenanceMCP server for paid business data services with free previews and paid tools (enriched search and competitive analysis) using x402 payment flow via Pyrimid Protocol on Base.Last updated
Try in Browser
Your Connectors
Sign in to create a connector for this server.