A
licenseNot graded
qualityC
maintenanceProvides MCP tools to check a package's maintenance status, licence, and security advisories before you depend on it, with per-call payment in USDC on Base mainnet via x402.
62
MIT
app-store-version
Server Details
Checks current App Store version by bundle ID. x402 payment required (testnet USDC).
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
1 toolapp_store_versionapp_store_versionAInspect
Checks current App Store version by bundle ID. x402 payment required (testnet USDC).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| country | No | 国コード(既定us) | |
| payment | No | x402 payment payload (base64 JSON), signed EIP-712 exact/transferWithAuthorization. Omit on the first call — the tool will return payment requirements (accepts[]) as an error result. | |
| maxItems | No | ||
| bundleIds | Yes | App StoreのbundleId配列 |
TDQS
A3.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the unusual payment requirement but doesn't explain that the first call is expected to fail and return payment requirements as an error result. Since annotations are absent, the description carries the full behavioral disclosure burden and only partially meets it.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences with no filler. The core function and the most important constraint (payment) are front-loaded. Every word earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool's purpose and payment requirement are clear, but the two-step payment handshake is not spelled out in the description. The country and maxItems parameters are only minimally described in the schema, and the description doesn't compensate. Still, the core operation is adequately covered.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 75%, and the payment parameter is well documented with the two-step behavior. The description adds value by clarifying the payment currency (testnet USDC) and framing the tool's purpose around App Store version checking.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific action ('Checks current App Store version') and a specific input mechanism (bundle ID). It doesn't name sibling tools to differentiate from, but no siblings are listed, so the clarity is sufficient for selection.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description includes practical usage context by noting 'x402 payment required (testnet USDC)'. However, it doesn't explicitly describe the two-step payment flow (omit payment first, then receive requirements and retry), which is only implied by the schema's payment parameter description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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 Connectors
9 App Store endpoints. Pay per call in USDC via x402.
Resolves real semver range satisfaction (^1.2.3, ~2.0) against a version. Paid via x402/USDC.
Tests an AI agent's purchase against the task it was given. Paid per call in USDC via x402.
Pay-per-use web extract, token prices, and wallet balances via x402 USDC micropayments.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables real-time cryptocurrency price lookups for 10,000+ tokens, returning 24h change, market cap, and volume via CoinGecko with x402 micropayment-based pay-per-call access.MIT
- AlicenseNot gradedqualityBmaintenanceEnables checking liquidity depth for Solana DEX pools (Raydium, Orca, Meteora) via pay-per-call x402 micropayments. Returns TVL, slippage estimates, volume, and fee tier for a given token mint.MIT
- AlicenseNot gradedqualityBmaintenancePaid Arbitrum transaction simulation, gas estimation, approval detection and risk scoring for wallets, bots and AI agents. Pay per check with USDC through MPP or x402.56MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.9/5.0
Disambiguation5/5
Only one tool exists, so there is no possibility of confusing its purpose with another tool. The tool description clearly explains what it checks and what input it requires.
Naming Consistency4/5
The single tool name uses snake_case and is internally consistent, but it omits a verb prefix (e.g., 'get_), which deviates from the typical verb_noun naming pattern. With only one tool, a stronger pattern cannot be established.
Tool Count4/5
A single tool is slightly below the typical 3-15 range, but the server's stated purpose is extremely narrow—checking an App Store version by bundle ID—so one tool feels reasonably scoped. It is not excessive or wildly incomplete for this domain.
Completeness5/5
For the stated purpose of checking the current App Store version by bundle ID, there are no obvious missing operations. The tool fully satisfies the narrow domain without leaving functional dead ends.