x402 Gateway — Inspect Paid API Terms

Server Details

Discover x402 paid APIs and inspect fresh payment requirements before authorizing spend.

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: 2026-09-06 08:17
Transport: Streamable HTTP
URL
Server Listing: mcp-x402

Available Tools

3 tools

sml_discoverBInspect

Find the x402 Gateway contract and where to inspect fresh payment requirements. FREE.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

B3.2/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. 'Find' and 'inspect' imply a read-only discovery operation, and 'FREE' suggests no cost, but the description does not mention return format, side effects, authentication needs, rate limits, or what happens if the contract is not found.

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?

The description is extremely concise: two purpose clauses and 'FREE.' It front-loads the primary action and adds only a brief useful qualifier. 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?

For a zero-parameter discovery tool, the description adequately states what the agent will get: the gateway contract and where to inspect payment requirements. However, with no output schema and no annotations, it does not describe the shape or format of the returned data, which is a notable gap.

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?

The tool has zero parameters and the schema is empty, so the description does not need to explain parameters. Baseline for zero-parameter tools is 4, and no ambiguity exists.

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 uses a specific verb ('Find') with a clear resource ('x402 Gateway contract') and adds a second deliverable ('where to inspect fresh payment requirements'). It is not a tautology and conveys a distinct purpose, though it does not explicitly differentiate itself from sibling tools like x402_contract.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for discovering the gateway contract and payment inspection location, but it provides no guidance on when to prefer this tool over sml_status or x402_contract, and no when-not-to-use conditions. The only extra hint is 'FREE,' which is not usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

sml_statusAInspect

Check the public x402 Gateway identity and canonical payment rail. FREE.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A3.5/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that the endpoint is public and free, which addresses auth and cost expectations. However, it does not disclose response format, rate limits, or whether any side effects occur.

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?

The description is a single sentence with key facts front-loaded; 'FREE' adds a useful cost signal without bloat. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter status check, the description gives enough information to invoke it correctly: it states what is checked and that it is public and free. It omits output schema details, but no output schema exists, so the agent may need to infer the response shape; this is a minor gap.

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?

The tool accepts zero parameters and schema coverage is 100% vacuously, so there are no parameter semantics to explain. The no-parameter baseline of 4 applies.

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 uses a specific verb 'check' and identifies the resource clearly: public x402 Gateway identity and canonical payment rail. It clearly establishes the tool's function, though it does not explicitly distinguish itself from siblings sml_discover or x402_contract.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus sml_discover or x402_contract. The 'FREE' note is about cost, not selection criteria, and there are no exclusions or prerequisites mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

x402_contractAInspect

Inspect the canonical x402 payment contract. Returns network, USDC asset, payTo, headers, and the rule for resolving fresh target requirements. FREE.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden of behavioral disclosure. It clearly indicates a read-only inspection, enumerates the returned data categories, and flags that the operation is free. It does not disclose rate limits or authentication, but for a zero-parameter inspection tool this is reasonably transparent.

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?

The description is two short sentences with no filler. It front-loads the core purpose, adds return-value detail, and ends with a useful cost signal. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless read-only tool with no output schema, the description provides the essential invocation context and a useful list of return categories. The phrase 'the rule for resolving fresh target requirements' is somewhat vague, but it is sufficient for an agent to know what the tool offers.

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?

The tool has zero parameters, so there is nothing for the description to clarify beyond what the schema shows. A baseline of 4 is appropriate since no parameter documentation burden exists.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Inspect') and a specific resource ('the canonical x402 payment contract'), and further clarifies by listing what it returns. This is enough to distinguish it from siblings like sml_discover or sml_status, even without explicit contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to use this tool versus alternatives, and no mention of exclusions or prerequisites. The intended use is implied by the resource name, but the description does not help an agent decide between this and sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

98 tool updatesSep 5, 2026
- Removedagentcard_lookup
- Removedagentcard_mint
- Removedagentcard_verify
- Removedapm_execute
- Removedapm_negotiate
- Removedbacktest_run
- Removedbacktest_validate
- Removedbeacon_scout
- Removedcopytrader_status
- Removedcopytrader_subscribe
- Removedcopytrader_whales
- Removedcrawl_paid_fetch
- Removedcrypto_token_price
- Removedcrypto_trending
- Removedequities_heatmap_full
- Removedequities_heatmap_preview
- Removedfederal_clinical_trials
- Removedfederal_congress_bills
- Removedfederal_drug_adverse_events
- Removedfederal_drug_label
- Removedfederal_drug_recall
- Removedfederal_entity_compliance
- Removedfederal_epa_violations
- Removedfederal_fec_finance
- Removedfederal_finra_broker
- Removedfederal_grants
- Removedfederal_grants_gov
- Removedfederal_insider_trades
- Removedfederal_lobbying
- Removedfederal_npi_lookup
- Removedfederal_options_flow
- Removedfederal_osha
- Removedfederal_patents
- Removedfederal_sam_entity
- Removedfederal_sam_opportunities
- Removedfederal_sba_awards
- Removedfederal_sbir_grants
- Removedfederal_sec_filings
- Removedfederal_treasury_yields
- Removedfederal_usaspending_awards
- Removedforge_llm
- Removedforge_status
- Removedftd_threshold_scan
- Removedfx_exchange_rate
- Removedget_agent_magnet_beacons
- Removedget_beacon_passport
- Removedget_beacon_score
- Removedghost_route
- Removedghost_status
- Removedhcv_fmr
- Removedhousing_landlord_checklist
- Removedhud_vash_contacts
- Removedlaunchpad_buy
- Removedlaunchpad_create
- Removedlaunchpad_list
- Removedlaunchpad_status
- Removedleviathan_signal
- Removedlist_magnets
- Removednexus_agent_hire
- Removedoptions_delta_heatmap_full
- Removedoptions_delta_heatmap_preview
- Removedpha_lookup
- Removedpha_opportunities
- Removedpha_search
- Removedproof_credit_score
- Removedproof_invoice
- Removedproof_verify
- Removedrails_status
- Removedrails_transfer
- Removedrobinhood_order
- Removedrobinhood_portfolio
- Removedrobinhood_quote
- Removedscreen_restricted_party
- Removedsearch_trade_leads
- Removedsection8_fmr
- Removedsection8_geo_lookup
- Removedsection8_income_limits
- Removedshadow_ingest
- Removedshadow_query
- Removedsqueezeos_council
- Removedsqueezeos_demo
- Removedsqueezeos_ftd
- Removedsqueezeos_futures_leaderboard
- Removedsqueezeos_history
- Removedsqueezeos_iwm
- Removedsqueezeos_marketplace_browse
- Removedsqueezeos_marketplace_read
- Removedsqueezeos_options
- Removedsqueezeos_oracle
- Removedsqueezeos_preview
- Removedsqueezeos_scan
- Removedsqueezeos_status
- Removedtradier_order
- Removedtradier_positions
- Removedtradier_quote
- Addedx402_contract
- Removedxdeo_earnings_estimate
- Removedxmit_edgar_decode
235 tool updatesSep 2, 2026
- Addedagentcard_lookup
- Addedagentcard_mint
- Addedagentcard_verify
- Removedai_fact_check
- Removedairdrop_check
- Addedapm_execute
- Addedapm_negotiate
- Changedbacktest_run10 fields changed
  - addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
  - changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```
  - addedInput schema / properties / fees
```
Added value: +{
+  "description": "Round-trip commission rate (default 0.001 = 0.1%)",
+  "type": "number"
+}
```
  - addedInput schema / properties / lookback_days
```
Added value: +{
+  "description": "Days of history to backtest (30–1260, default 252)",
+  "type": "number"
+}
```
  - addedInput schema / properties / momentum_threshold
```
Added value: +{
+  "description": "Minimum momentum to enter long (default 0.001)",
+  "type": "number"
+}
```
  - addedInput schema / properties / momentum_window
```
Added value: +{
+  "description": "Momentum rolling window in days (default 10)",
+  "type": "number"
+}
```
  - addedInput schema / properties / slippage
```
Added value: +{
+  "description": "Slippage per side (default 0.0005)",
+  "type": "number"
+}
```
  - addedInput schema / properties / ticker
```
Added value: +{
+  "description": "Ticker symbol (e.g. NVDA, SPY, GME)",
+  "type": "string"
+}
```
  - addedInput schema / properties / wallet_address
```
Added value: +{
+  "description": "Agent wallet address (optional)",
+  "type": "string"
+}
```
  - changedInput schema / required
```
Previous value: -[]New value: +[
+  "ticker",
+  "lookback_days",
+  "fees",
+  "slippage",
+  "momentum_window",
+  "momentum_threshold",
+  "wallet_address"
+]
```
- Removedbacktest_strategies
- Removedbacktest_sweep
- Addedbacktest_validate
- Removedbase_rpc
- Removedbase64_encode
- Addedbeacon_scout
- Removedbinance_funding
- Removedbinance_ticker
- Removedbtc_mempool_fees
- Removedbtc_price
- Removedcalculator
- Removedclinical_trials_search
- Removedcoingecko_categories
- Removedcompliance_anomaly_report
- Removedcompliance_bank_audit
- Removedcompliance_regulator_query
- Removedcongressional_bills_search
- Addedcopytrader_status
- Addedcopytrader_subscribe
- Addedcopytrader_whales
- Addedcrawl_paid_fetch
- Removedcrypto_global
- Removedcrypto_news
- Removedcrypto_penny_squeeze_scanner
- Removedcrypto_price
- Removedcrypto_squeeze_scanner
- Addedcrypto_token_price
- Addedcrypto_trending
- Removedcsv_to_json
- Removeddefi_analytics
- Removeddefi_chains_tvl
- Removeddefi_protocol_tvl
- Removeddefi_tvl_ranking
- Removeddefi_yield
- Removeddefi_yield_rates
- Removeddefi_yields_pools
- Removeddexscreener_boosts
- Removeddexscreener_search
- Removeddomain_enrich
- Removeddruckenmiller_macro_regime_analysis
- Removedemail_validate
- Removedentity_compliance_check
- Removedepa_environmental_violations
- Addedequities_heatmap_full
- Addedequities_heatmap_preview
- Removedeth_price
- Removedeth_rpc
- Removedexcluded_parties_check
- Removedfda_adverse_events_report
- Removedfda_drug_recall_alert
- Removedfda_food_recalls
- Removedfda_warning_letters
- Removedfear_greed_index
- Removedfec_campaign_finance
- Removedfederal_award_history
- Addedfederal_clinical_trials
- Addedfederal_congress_bills
- Removedfederal_contract_opportunities
- Addedfederal_drug_adverse_events
- Addedfederal_drug_label
- Addedfederal_drug_recall
- Addedfederal_entity_compliance
- Addedfederal_epa_violations
- Addedfederal_fec_finance
- Addedfederal_finra_broker
- Addedfederal_grants
- Addedfederal_grants_gov
- Addedfederal_insider_trades
- Addedfederal_lobbying
- Addedfederal_npi_lookup
- Addedfederal_options_flow
- Addedfederal_osha
- Addedfederal_patents
- Addedfederal_sam_entity
- Addedfederal_sam_opportunities
- Addedfederal_sba_awards
- Addedfederal_sbir_grants
- Addedfederal_sec_filings
- Removedfederal_spending_by_agency
- Addedfederal_treasury_yields
- Addedfederal_usaspending_awards
- Addedforge_llm
- Addedforge_status
- Removedfred_economic_indicators
- Addedftd_threshold_scan
- Removedfunding_rates
- Addedfx_exchange_rate
- Removedfx_rate
- Removedgas_tracker
- Removedgeckoterminal_trending
- Changedget_agent_magnet_beacons5 fields changed
  - addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
  - changedInput schema / properties / limit / description
```
Previous value: -"Optional max paid beacons."New value: +"Optional max paid+free beacons in the set."
```
  - addedInput schema / properties / limit / maximum
```
Added value: +500
```
  - addedInput schema / properties / limit / minimum
```
Added value: +1
```
  - removedInput schema / required
```
Removed value: -[]
```
- Addedget_beacon_passport
- Addedget_beacon_score
- Addedghost_route
- Addedghost_status
- Removedhash_compute
- Addedhcv_fmr
- Removedhex_convert
- Removedhmac_compute
- Removedhoneypot_check
- Addedhousing_landlord_checklist
- Removedhttp_check
- Addedhud_vash_contacts
- Removedhyperliquid_all_mids
- Removedhyperliquid_meta
- Removedip_info
- Removedjson_to_csv
- Removedjson_to_yaml
- Removedjson_validate
- Removedjwt_decode
- Removedkeyword_extract
- Removedl2_activity
- Addedlaunchpad_buy
- Addedlaunchpad_create
- Addedlaunchpad_list
- Addedlaunchpad_status
- Addedleviathan_signal
- Removedliquidation_risk_check
- Changedlist_magnets9 fields changed
  - addedInput schema / $schema
```
Added value: +"http://json-schema.org/draft-07/schema#"
```
  - addedInput schema / properties / limit / maximum
```
Added value: +200
```
  - addedInput schema / properties / limit / minimum
```
Added value: +1
```
  - addedInput schema / properties / min_imp_score
```
Added value: +{
+  "description": "Minimum IMP imp_score filter 0-1 (preferred).",
+  "maximum": 1,
+  "minimum": 0,
+  "type": "number"
+}
```
  - changedInput schema / properties / min_strength / description
```
Previous value: -"Minimum magnet_strength 0-1 filter."New value: +"Minimum magnet_strength filter 0-1 (legacy)."
```
  - addedInput schema / properties / min_strength / maximum
```
Added value: +1
```
  - addedInput schema / properties / min_strength / minimum
```
Added value: +0
```
  - addedInput schema / properties / sort
```
Added value: +{
+  "description": "Rank key (default imp_score).",
+  "enum": [
+    "imp_score",
+    "magnet_strength"
+  ],
+  "type": "string"
+}
```
  - removedInput schema / required
```
Removed value: -[]
```
- Removedllm_chat
- Removedlobbying_disclosures
- Removedmarket_regime_indicator
- Removednew_token_detection
- Removednews_headlines
- Addednexus_agent_hire
- Removednumber_format
- Removedopenfda_drug_label
- Addedoptions_delta_heatmap_full
- Addedoptions_delta_heatmap_preview
- Removedosha_inspection_records
- Removedpenny_squeeze_scanner
- Removedpercentage
- Removedperp_funding_aggregator
- Addedpha_lookup
- Addedpha_opportunities
- Addedpha_search
- Addedproof_credit_score
- Addedproof_invoice
- Addedproof_verify
- Addedrails_status
- Addedrails_transfer
- Removedregex_test
- Addedrobinhood_order
- Addedrobinhood_portfolio
- Addedrobinhood_quote
- Removedrobots_check
- Removedrugpull_detector
- Removedrwa_aggregates
- Removedrwa_assets
- Removedrwa_intelligence
- Removedrwa_risk
- Removedrwa_valuation
- Removedsam_entity_verification
- Removedsam_opportunities
- Addedscreen_restricted_party
- Removedsdvosb_setaside_feed
- Addedsearch_trade_leads
- Removedsec_10_k_annual_filing
- Removedsec_10_q_quarterly_filing
- Removedsec_13d_13g_activist_filings
- Removedsec_13f_institutional_holdings
- Removedsec_8_k_real_time_filings
- Removedsec_company_tickers
- Removedsec_insider_trade_intel
- Addedsection8_fmr
- Addedsection8_geo_lookup
- Addedsection8_income_limits
- Removedsemver_compare
- Addedshadow_ingest
- Addedshadow_query
- Removedsitemap_reader
- Removedsmart_money_alerts
- Addedsml_discover
- Addedsml_status
- Removedsocial_search
- Removedsol_price
- Removedsqueeze_scanner
- Addedsqueezeos_council
- Addedsqueezeos_demo
- Addedsqueezeos_ftd
- Addedsqueezeos_futures_leaderboard
- Addedsqueezeos_history
- Addedsqueezeos_iwm
- Addedsqueezeos_marketplace_browse
- Addedsqueezeos_marketplace_read
- Addedsqueezeos_options
- Addedsqueezeos_oracle
- Addedsqueezeos_preview
- Addedsqueezeos_scan
- Addedsqueezeos_status
- Removedstablecoin_flow_tracker
- Removedstablecoin_mcap
- Removedstablecoin_watch
- Removedstatistics
- Removedtext_case_convert
- Removedtext_diff
- Removedtext_slugify
- Removedtext_stats
- Removedtls_cert
- Removedtoken_details
- Removedtoken_security_audit
- Removedtoken_top_markets
- Addedtradier_order
- Addedtradier_positions
- Addedtradier_quote
- Removedtreasury_yields
- Removedtrending_altcoins
- Removedtrending_tokens
- Removedtx_status
- Removedunit_convert
- Removedurl_parse
- Removedus_gov_search
- Removedus_weather_alerts
- Removedusdc_balance
- Removeduseragent_parse
- Removedusgs_earthquakes
- Removedwallet_analysis
- Removedwallet_analyzer
- Removedweb_fetch
- Removedweb_markdown
- Removedweb_search
- Removedwhois_rdap
- Removedx402_market_pulse
- Addedxdeo_earnings_estimate
- Addedxmit_edgar_decode
- Removedxml_to_json
- Removedyaml_to_json
3 tool updatesAug 8, 2026
- Addedbacktest_run
- Addedbacktest_strategies
- Addedbacktest_sweep
136 tool updatesAug 8, 2026
- First observedai_fact_check
- First observedairdrop_check
- First observedbase_rpc
- First observedbase64_encode
- First observedbinance_funding
- First observedbinance_ticker
- First observedbtc_mempool_fees
- First observedbtc_price
- First observedcalculator
- First observedclinical_trials_search
- First observedcoingecko_categories
- First observedcompliance_anomaly_report
- First observedcompliance_bank_audit
- First observedcompliance_regulator_query
- First observedcongressional_bills_search
- First observedcrypto_global
- First observedcrypto_news
- First observedcrypto_penny_squeeze_scanner
- First observedcrypto_price
- First observedcrypto_squeeze_scanner
- First observedcsv_to_json
- First observeddefi_analytics
- First observeddefi_chains_tvl
- First observeddefi_protocol_tvl
- First observeddefi_tvl_ranking
- First observeddefi_yield
- First observeddefi_yield_rates
- First observeddefi_yields_pools
- First observeddexscreener_boosts
- First observeddexscreener_search
- First observeddomain_enrich
- First observeddruckenmiller_macro_regime_analysis
- First observedemail_validate
- First observedentity_compliance_check
- First observedepa_environmental_violations
- First observedeth_price
- First observedeth_rpc
- First observedexcluded_parties_check
- First observedfda_adverse_events_report
- First observedfda_drug_recall_alert
- First observedfda_food_recalls
- First observedfda_warning_letters
- First observedfear_greed_index
- First observedfec_campaign_finance
- First observedfederal_award_history
- First observedfederal_contract_opportunities
- First observedfederal_spending_by_agency
- First observedfred_economic_indicators
- First observedfunding_rates
- First observedfx_rate
- First observedgas_tracker
- First observedgeckoterminal_trending
- First observedget_agent_magnet_beacons
- First observedhash_compute
- First observedhex_convert
- First observedhmac_compute
- First observedhoneypot_check
- First observedhttp_check
- First observedhyperliquid_all_mids
- First observedhyperliquid_meta
- First observedip_info
- First observedjson_to_csv
- First observedjson_to_yaml
- First observedjson_validate
- First observedjwt_decode
- First observedkeyword_extract
- First observedl2_activity
- First observedliquidation_risk_check
- First observedlist_magnets
- First observedllm_chat
- First observedlobbying_disclosures
- First observedmarket_regime_indicator
- First observednew_token_detection
- First observednews_headlines
- First observednumber_format
- First observedopenfda_drug_label
- First observedosha_inspection_records
- First observedpenny_squeeze_scanner
- First observedpercentage
- First observedperp_funding_aggregator
- First observedregex_test
- First observedrobots_check
- First observedrugpull_detector
- First observedrwa_aggregates
- First observedrwa_assets
- First observedrwa_intelligence
- First observedrwa_risk
- First observedrwa_valuation
- First observedsam_entity_verification
- First observedsam_opportunities
- First observedsdvosb_setaside_feed
- First observedsec_10_k_annual_filing
- First observedsec_10_q_quarterly_filing
- First observedsec_13d_13g_activist_filings
- First observedsec_13f_institutional_holdings
- First observedsec_8_k_real_time_filings
- First observedsec_company_tickers
- First observedsec_insider_trade_intel
- First observedsemver_compare
- First observedsitemap_reader
- First observedsmart_money_alerts
- First observedsocial_search
- First observedsol_price
- First observedsqueeze_scanner
- First observedstablecoin_flow_tracker
- First observedstablecoin_mcap
- First observedstablecoin_watch
- First observedstatistics
- First observedtext_case_convert
- First observedtext_diff
- First observedtext_slugify
- First observedtext_stats
- First observedtls_cert
- First observedtoken_details
- First observedtoken_security_audit
- First observedtoken_top_markets
- First observedtreasury_yields
- First observedtrending_altcoins
- First observedtrending_tokens
- First observedtx_status
- First observedunit_convert
- First observedurl_parse
- First observedus_gov_search
- First observedus_weather_alerts
- First observedusdc_balance
- First observeduseragent_parse
- First observedusgs_earthquakes
- First observedwallet_analysis
- First observedwallet_analyzer
- First observedweb_fetch
- First observedweb_markdown
- First observedweb_search
- First observedwhois_rdap
- First observedx402_market_pulse
- First observedxml_to_json
- First observedyaml_to_json

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, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
- HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on 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.

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Connectors

GhostKey — Route Paid APIs with x402 A
com.scriptmasterlabs
Find paid APIs, check access policy and price, and route x402 requests. No autonomous spending.
Autonomous Agents Payments & Billing
41
graded-x402 B
sh.graded
Discover and call 2,000+ x402 machine-payable services through one graded API key + gateway.
Payments & Billing Developer Tools
1
code402 A
io.github.89rat
Discover machine-payable APIs, probe x402 payment terms, and run seller operations. Non-custodial.
Payments & Billing
101
foragex402 A
io.github.mapizarro1
Meta-search MCP for x402 agent-payable services -- find paid APIs across every registry.
Search Developer Tools
22

Related MCP Servers

x402-discovery
Blockchain Cryptocurrency Autonomous Agents
rplryan
A
license
Not graded
quality
D
maintenance
Discovers and queries x402-payable APIs at runtime — enables autonomous agents to find, evaluate, and pay for services via USDC micropayments on Base without API keys or subscriptions.
Updated a month ago (2026-08-04 12:33 UTC)
MIT
nohumans-mcp
Search Monitoring Payments & Billing
jalcodev
F
license
Not graded
quality
B
maintenance
Find and vet paid x402 API services before an agent spends money on them, with live reliability scores and recency-weighted probing.
Updated 6 days ago (2026-08-31 18:45 UTC)
-
agent-tools-mcp
Agent Orchestration Search
JoursBleu
A
license
Not graded
quality
C
maintenance
Enables MCP-compatible agents to discover and call x402 paid services from a directory of over 2,000 APIs.
Updated 3 months ago (2026-05-29 04:42 UTC)
Apache 2.0
x402 Preflight
Autonomous Agents Payments & Billing Security
chico10117
F
license
Not graded
quality
B
maintenance
Enables autonomous agents to inspect and audit unfamiliar x402 endpoints before spending USDC, using bounded read-only probes to surface payment challenges, pricing, network, receiver, and operational signals without signing or spending funds.
Updated 2 days ago (2026-09-04 20:18 UTC)
-

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0

Disambiguation4/5

Each tool has a distinct role: discover locates the gateway and requirement sources, status checks the live identity and payment rail, and contract inspects the on-chain details. There is minor overlap between discover and contract, but the descriptions clearly differentiate their intentions.

Naming Consistency2/5

Naming is inconsistent: two tools use the 'sml_' prefix while the third uses 'x402_', and the suffix styles mix a verb (discover) with nouns (status, contract). This makes the set feel less predictable and harder to scan.

Tool Count4/5

Three tools is lean but well-suited for the narrow domain of x402 gateway discovery and inspection. Each tool earns its place, and the count feels appropriate rather than sparse or bloated.

Completeness4/5

The tools cover discovery, live status, and on-chain contract inspection, which appears to be the full intended scope for this gateway-focused server. No obvious missing operations are apparent from the stated purpose.

Server Details

Available Tools

Tool Schema Changelog

Frequently Asked Questions

Discussions

Related MCP Connectors

Related MCP Servers

Glama MCP Gateway

Resources