Skip to main content
Glama

PPN Hub — public APIs over MCP

by com.ppn-hub
OverviewDiscussionsAdmin

Server Details

One MCP endpoint over 69 public PPN APIs: search_apis to discover, execute_api to call. Free tier.

Ownership verified
Status
Healthy
Uptime
100.0% over 75 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation4/5

search_apis (discovery), execute_api (generic invocation), and environment_brief (composite geo fan-out) occupy mostly distinct roles. environment_brief overlaps somewhat with execute_api since the same weather/geo endpoints can be called directly, but the aggregation intent is clearly stated.

Naming Consistency3/5

execute_api and search_apis follow a consistent verb_noun snake_case pattern, but environment_brief is a noun_phrase that breaks the convention. Names remain readable and snake_case throughout, so it's a mixed-but-parseable set.

Tool Count4/5

Three tools is lean but appropriate for a gateway/proxy pattern: one discovery tool, one executor, and one composite convenience tool. The 519-endpoint surface is intentionally funneled through search+execute rather than one tool per API.

Completeness4/5

Discovery (search_apis) plus invocation (execute_api) covers the core gateway lifecycle, and environment_brief adds a useful composite. Minor gaps like no direct API/endpoint listing or auth/session management tooling, but agents can work around these via search.

Available Tools

3 tools
environment_briefAInspect

Environmental brief for one location: fans out to every public geo-aware API (weather, terrain, environment, …) and returns a merged JSON. Partial results come back with an errors[] list. Requires 'Authorization: Bearer ppn_live_*'.

NameRequiredDescriptionDefault
latYesLatitude
lonYesLongitude
placeNoOptional human-readable place label (echoed back)

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description compensates by disclosing key behaviors: it fans out to multiple APIs, returns merged JSON, handles partial results with an errors[] list, and requires authorization. This is substantial transparency, though it omits details like rate limits or latency.

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 very concise with three sentences, each adding essential information: behavior, error handling, and authentication. No redundant or vague phrasing.

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?

Given the lack of output schema and annotations, the description covers the main functionality and error reporting, but does not describe the structure of the merged JSON output or any constraints on usage, leaving some aspects incomplete for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and descriptions in the schema already explain lat, lon, and place adequately. The tool description adds no new semantic information beyond what the schema provides, so the default score of 3 is appropriate.

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 clearly states it provides an 'Environmental brief for one location' by aggregating multiple APIs, and the name 'environment_brief' reinforces this. It distinguishes from the broader sibling tools 'execute_api' and 'search_apis' by being specialized and self-contained.

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 mentions it requires a specific authorization token, but does not explicitly state when to use this tool versus alternatives, nor provides any exclusion criteria. Usage is implied for environmental data retrieval but lacks explicit guidance.

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

execute_apiAInspect

Execute a request against any of the 60 registered APIs. Use search_apis first to find the correct api name and operationId. Requires 'Authorization: Bearer ppn_live_*'.

NameRequiredDescriptionDefault
apiYesAPI name: sanken-matrix-gateway, marketo, atmos, chronomap, hydros, lithos, terra, carbon-credit, cost-compare, demand-forecast, grid-connect, site-matching, storage-optimize, tariff-optimize, transmission-loss, carbonias, planetary, green-path-api, biomassia, gasturbia, geothermia, hydria, reactoria, renewio, solaria, windaria-api, hydrogen, sla-viewer-production, nanobase-api, nanosnap-console, nanosnap-gacha-production, nanosnap-inventory-production, nanosnap-leaderboard-production, nanosnap-mailbox-production, nanosnap-persona-gateway-production, nanosnap-presence-production, nanosnap-replay-production, nanosnap-room-production, nanosnap-save-data-production, nanosnap-spatial-message-production, nanosnap-world-counter-production, nanosnap-world-objects-production, biositia, cryonia, faunaunify, literatia, plantunify, ppn-hub-workers, foodsense, onokoro, sakurahub-address, sakurahub-gateway, sakurahub-web, weathio, biolexia-production, biocolo, nishinoshima-gateway-production, celestora, orbitalio, perks
bodyNoRequest body for POST/PUT/PATCH
paramsNoQuery and path parameters as key-value pairs
operationIdYesoperationId from search_apis results

TDQS

A3.9/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, and it does disclose the required auth scheme ('Authorization: Bearer ppn_live_*'), which is genuinely useful. However, it says nothing about the fact that arbitrary operations (including destructive writes via POST/PUT/PATCH) can be issued against 60 APIs, nor about error handling, rate limits, or side effects.

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?

Three short sentences, zero filler, and the most important operational facts (what it does, the search_apis prerequisite, the auth requirement) are front-loaded in that order.

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 generic multi-API executor with no annotations and no output schema, the description covers the calling workflow and auth but omits mutation semantics, response shape, and failure behavior. Adequate to invoke correctly, but thin given the tool's broad and potentially destructive surface.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents api, operationId, body, and params, establishing a baseline of 3. The description reinforces the provenance of api/operationId (from search_apis results) but adds no syntax or format detail beyond what the schema provides.

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?

States a specific verb (execute) and resource (a request against one of 60 registered APIs), and scopes it precisely enough that it is immediately distinguishable from the sibling search_apis, which the description explicitly frames as a lookup step rather than a substitute.

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

Usage Guidelines4/5

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

Explicitly tells the agent to call search_apis first to obtain the correct api name and operationId, which is the exact prerequisite workflow needed. It stops short of stating when NOT to use this tool (e.g., for read-only discovery or environment inspection via environment_brief).

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

search_apisAInspect

Search across 519 endpoints in 60 APIs (amenomi, cultural, earth, energy-calc, green-path, harmonias, hydrogen, internal, nanobase, nanosnap, natura, platform, sakurahub, science, sim, space, stocks). Returns matching endpoints with method, path, summary, parameters, and a ready-to-run example. Use this to discover available API endpoints before calling execute_api. Results carry a "coverage" field (e.g. ["JP"]) for region-limited APIs; use the "region" filter to narrow.

NameRequiredDescriptionDefault
tagNoFilter by OpenAPI tag
limitNoMax results (default: 20)
queryYesSearch term (matches operationId, summary, description, path, API name, tags; synonyms expanded)
domainNoFilter by domain: amenomi, cultural, earth, energy-calc, green-path, harmonias, hydrogen, internal, nanobase, nanosnap, natura, platform, sakurahub, science, sim, space, stocks
methodNoFilter by HTTP method
regionNoFilter by ISO 3166-1 alpha-2 region the API serves data for (e.g. "JP"). Returns region-specific + global APIs; excludes APIs limited to other regions.

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the shape of results (method, path, summary, parameters, ready-to-run example) and the semantics of the "coverage" field for region-limited APIs. It does not mention auth requirements, rate limits, or whether results are cached/paginated, which keeps it below 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with scope, then return shape, then routing, then region caveat – a logical order with no filler. The inline list of 17 domain names duplicates the domain parameter enum in the schema and is the one piece of avoidable bulk.

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?

There is no output schema, so the description must describe returns, and it does: matching endpoints plus a ready-to-run example, with the coverage field explained. Combined with the execute_api routing, an agent has what it needs to call this correctly; only operational details like limits or auth are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all six parameters are already documented in the schema, including the region filter's exact behavior. The description's mention of the region filter and coverage field largely restates schema content, so the baseline 3 applies.

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?

States a specific verb (search) and resource (API endpoints) and quantifies scope: 519 endpoints across 60 named APIs. It also names the sibling it feeds into (execute_api), so an agent can distinguish it from execute_api and environment_brief without opening any schema.

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

Usage Guidelines4/5

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

Explicitly routes the agent: "Use this to discover available API endpoints before calling execute_api." This gives a clear when-to-use condition tied to a named alternative. It lacks an explicit when-not/negative case (e.g., when to skip discovery), so it falls short of a 5.

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.

  1. 2 tool updates
    • Changedexecute_api1 field changed
      • changedInput schema / properties / api / description
        Previous value: -"API name: marketo, atmos, chronomap, hydros, lithos, terra, carbon-credit, cost-compare, demand-forecast, grid-connect, site-matching, storage-optimize, tariff-optimize, transmission-loss, carbonias, planetary, green-path-api, biomassia, gasturbia, geothermia, hydria, reactoria, renewio, solaria, windaria-api, hydrogen, sla-viewer-production, nanobase-api, nanosnap-console, nanosnap-gacha-production, nanosnap-inventory-production, nanosnap-leaderboard-production, nanosnap-mailbox-production, nanosnap-persona-gateway-production, nanosnap-presence-production, nanosnap-replay-production, nanosnap-room-production, nanosnap-save-data-production, nanosnap-spatial-message-production, nanosnap-world-counter-production, nanosnap-world-objects-production, biositia, cryonia, faunaunify, literatia, plantunify, ppn-hub-workers, foodsense, onokoro, sakurahub-address, sakurahub-gateway, sakurahub-web, weathio, biolexia-production, biocolo, nishinoshima-gateway-production, celestora, orbitalio, perks"New value: +"API name: sanken-matrix-gateway, marketo, atmos, chronomap, hydros, lithos, terra, carbon-credit, cost-compare, demand-forecast, grid-connect, site-matching, storage-optimize, tariff-optimize, transmission-loss, carbonias, planetary, green-path-api, biomassia, gasturbia, geothermia, hydria, reactoria, renewio, solaria, windaria-api, hydrogen, sla-viewer-production, nanobase-api, nanosnap-console, nanosnap-gacha-production, nanosnap-inventory-production, nanosnap-leaderboard-production, nanosnap-mailbox-production, nanosnap-persona-gateway-production, nanosnap-presence-production, nanosnap-replay-production, nanosnap-room-production, nanosnap-save-data-production, nanosnap-spatial-message-production, nanosnap-world-counter-production, nanosnap-world-objects-production, biositia, cryonia, faunaunify, literatia, plantunify, ppn-hub-workers, foodsense, onokoro, sakurahub-address, sakurahub-gateway, sakurahub-web, weathio, biolexia-production, biocolo, nishinoshima-gateway-production, celestora, orbitalio, perks"
    • Changedsearch_apis1 field changed
      • changedInput schema / properties / domain / description
        Previous value: -"Filter by domain: cultural, earth, energy-calc, green-path, harmonias, hydrogen, internal, nanobase, nanosnap, natura, platform, sakurahub, science, sim, space, stocks"New value: +"Filter by domain: amenomi, cultural, earth, energy-calc, green-path, harmonias, hydrogen, internal, nanobase, nanosnap, natura, platform, sakurahub, science, sim, space, stocks"
  2. 1 tool update
    • Changedexecute_api1 field changed
      • changedInput schema / properties / api / description
        Previous value: -"API name: marketo, atmos, chronomap, hydros, lithos, terra, carbon-credit, cost-compare, demand-forecast, grid-connect, site-matching, storage-optimize, tariff-optimize, transmission-loss, carbonias, planetary, green-path-api, biomassia, gasturbia, geothermia, hydria, reactoria, renewio, solaria, windaria-api, hydrogen, sla-viewer-production, nanobase-api, nanosnap-console, nanosnap-gacha-production, nanosnap-inventory-production, nanosnap-leaderboard-production, nanosnap-mailbox-production, nanosnap-persona-gateway-production, nanosnap-presence-production, nanosnap-replay-production, nanosnap-room-production, nanosnap-save-data-production, nanosnap-spatial-message-production, nanosnap-world-counter-production, nanosnap-world-objects-production, biositia, cryonia, faunaunify, literatia, plantunify, ppn-hub-workers, onokoro, sakurahub-address, sakurahub-gateway, sakurahub-web, weathio, biolexia-production, biocolo, nishinoshima-gateway-production, celestora, orbitalio, perks"New value: +"API name: marketo, atmos, chronomap, hydros, lithos, terra, carbon-credit, cost-compare, demand-forecast, grid-connect, site-matching, storage-optimize, tariff-optimize, transmission-loss, carbonias, planetary, green-path-api, biomassia, gasturbia, geothermia, hydria, reactoria, renewio, solaria, windaria-api, hydrogen, sla-viewer-production, nanobase-api, nanosnap-console, nanosnap-gacha-production, nanosnap-inventory-production, nanosnap-leaderboard-production, nanosnap-mailbox-production, nanosnap-persona-gateway-production, nanosnap-presence-production, nanosnap-replay-production, nanosnap-room-production, nanosnap-save-data-production, nanosnap-spatial-message-production, nanosnap-world-counter-production, nanosnap-world-objects-production, biositia, cryonia, faunaunify, literatia, plantunify, ppn-hub-workers, foodsense, onokoro, sakurahub-address, sakurahub-gateway, sakurahub-web, weathio, biolexia-production, biocolo, nishinoshima-gateway-production, celestora, orbitalio, perks"
  3. 2 tool updates
    • Changedexecute_api1 field changed
      • changedInput schema / properties / api / description
        Previous value: -"API name: artia, marketo, atmos, chronomap, hydros, lithos, terra, carbon-credit, cost-compare, demand-forecast, grid-connect, site-matching, storage-optimize, tariff-optimize, transmission-loss, carbonias, planetary, green-path-api, biomassia, gasturbia, geothermia, hydria, reactoria, renewio, solaria, windaria-api, hydrogen, sla-viewer-production, nanobase-api, nanosnap-console, nanosnap-gacha-production, nanosnap-inventory-production, nanosnap-leaderboard-production, nanosnap-mailbox-production, nanosnap-persona-gateway-production, nanosnap-presence-production, nanosnap-replay-production, nanosnap-room-production, nanosnap-save-data-production, nanosnap-spatial-message-production, nanosnap-world-counter-production, nanosnap-world-objects-production, biositia, biota, cryonia, faunaunify, insectunify, literatia, plantunify, ppn-hub-workers, onokoro, sakurahub-address, sakurahub-gateway, sakurahub-web, weathio, biolexia-production, science-climate, science-ecology, biocolo, nishinoshima-gateway-production, crime, disease, noise, traffic, celestora, orbitalio, perks"New value: +"API name: marketo, atmos, chronomap, hydros, lithos, terra, carbon-credit, cost-compare, demand-forecast, grid-connect, site-matching, storage-optimize, tariff-optimize, transmission-loss, carbonias, planetary, green-path-api, biomassia, gasturbia, geothermia, hydria, reactoria, renewio, solaria, windaria-api, hydrogen, sla-viewer-production, nanobase-api, nanosnap-console, nanosnap-gacha-production, nanosnap-inventory-production, nanosnap-leaderboard-production, nanosnap-mailbox-production, nanosnap-persona-gateway-production, nanosnap-presence-production, nanosnap-replay-production, nanosnap-room-production, nanosnap-save-data-production, nanosnap-spatial-message-production, nanosnap-world-counter-production, nanosnap-world-objects-production, biositia, cryonia, faunaunify, literatia, plantunify, ppn-hub-workers, onokoro, sakurahub-address, sakurahub-gateway, sakurahub-web, weathio, biolexia-production, biocolo, nishinoshima-gateway-production, celestora, orbitalio, perks"
    • Changedsearch_apis1 field changed
      • changedInput schema / properties / domain / description
        Previous value: -"Filter by domain: cultural, earth, energy-calc, green-path, harmonias, hydrogen, internal, nanobase, nanosnap, natura, platform, sakurahub, science, sim, social, space, stocks"New value: +"Filter by domain: cultural, earth, energy-calc, green-path, harmonias, hydrogen, internal, nanobase, nanosnap, natura, platform, sakurahub, science, sim, space, stocks"
  4. 1 tool update
    • Changedexecute_api1 field changed
      • changedInput schema / properties / api / description
        Previous value: -"API name: artia, marketo, atmos, chronomap, hydros, lithos, terra, carbon-credit, cost-compare, demand-forecast, grid-connect, site-matching, storage-optimize, tariff-optimize, transmission-loss, carbonias, planetary, green-path-api, biomassia, gasturbia, geothermia, hydria, reactoria, renewio, solaria, windaria-api, hydrogen, sla-viewer-production, nanobase-api, nanosnap-console, nanosnap-gacha-production, nanosnap-inventory-production, nanosnap-leaderboard-production, nanosnap-mailbox-production, nanosnap-persona-gateway-production, nanosnap-presence-production, nanosnap-replay-production, nanosnap-room-production, nanosnap-save-data-production, nanosnap-spatial-message-production, nanosnap-world-counter-production, nanosnap-world-objects-production, biositia, biota, cryonia, faunaunify, insectunify, literatia, plantunify, ppn-hub-workers, onokoro, sakurahub-address, sakurahub-gateway, sakurahub-web, weathio, biolexia-production, science-climate, science-ecology, science-geology, biocolo, nishinoshima-gateway-production, crime, disease, noise, traffic, celestora, orbitalio, perks"New value: +"API name: artia, marketo, atmos, chronomap, hydros, lithos, terra, carbon-credit, cost-compare, demand-forecast, grid-connect, site-matching, storage-optimize, tariff-optimize, transmission-loss, carbonias, planetary, green-path-api, biomassia, gasturbia, geothermia, hydria, reactoria, renewio, solaria, windaria-api, hydrogen, sla-viewer-production, nanobase-api, nanosnap-console, nanosnap-gacha-production, nanosnap-inventory-production, nanosnap-leaderboard-production, nanosnap-mailbox-production, nanosnap-persona-gateway-production, nanosnap-presence-production, nanosnap-replay-production, nanosnap-room-production, nanosnap-save-data-production, nanosnap-spatial-message-production, nanosnap-world-counter-production, nanosnap-world-objects-production, biositia, biota, cryonia, faunaunify, insectunify, literatia, plantunify, ppn-hub-workers, onokoro, sakurahub-address, sakurahub-gateway, sakurahub-web, weathio, biolexia-production, science-climate, science-ecology, biocolo, nishinoshima-gateway-production, crime, disease, noise, traffic, celestora, orbitalio, perks"
  5. 2 tool updates
    • Changedexecute_api1 field changed
      • changedInput schema / properties / api / description
        Previous value: -"API name: artia, marketo, atmos, chronomap, hydros, lithos, terra, carbon-credit, cost-compare, demand-forecast, grid-connect, site-matching, storage-optimize, tariff-optimize, transmission-loss, carbonias, planetary, green-path-api, biomassia, gasturbia, geothermia, hydria, reactoria, renewio, solaria, windaria-api, hydrogen, sla-viewer-production, nanobase-api, nanobase-console, nanosnap-console, nanosnap-gacha-production, nanosnap-inventory-production, nanosnap-leaderboard-production, nanosnap-mailbox-production, nanosnap-persona-gateway-production, nanosnap-presence-production, nanosnap-replay-production, nanosnap-room-production, nanosnap-save-data-production, nanosnap-spatial-message-production, nanosnap-world-counter-production, nanosnap-world-objects-production, biositia, biota, cryonia, faunaunify, insectunify, literatia, plantunify, ppn-hub-workers, onokoro, sakurahub-address, sakurahub-gateway, sakurahub-web, weathio, biolexia-production, science-climate, science-ecology, science-geology, biocolo, nishinoshima-gateway-production, crime, disease, noise, traffic, celestora, orbitalio, perks"New value: +"API name: artia, marketo, atmos, chronomap, hydros, lithos, terra, carbon-credit, cost-compare, demand-forecast, grid-connect, site-matching, storage-optimize, tariff-optimize, transmission-loss, carbonias, planetary, green-path-api, biomassia, gasturbia, geothermia, hydria, reactoria, renewio, solaria, windaria-api, hydrogen, sla-viewer-production, nanobase-api, nanosnap-console, nanosnap-gacha-production, nanosnap-inventory-production, nanosnap-leaderboard-production, nanosnap-mailbox-production, nanosnap-persona-gateway-production, nanosnap-presence-production, nanosnap-replay-production, nanosnap-room-production, nanosnap-save-data-production, nanosnap-spatial-message-production, nanosnap-world-counter-production, nanosnap-world-objects-production, biositia, biota, cryonia, faunaunify, insectunify, literatia, plantunify, ppn-hub-workers, onokoro, sakurahub-address, sakurahub-gateway, sakurahub-web, weathio, biolexia-production, science-climate, science-ecology, science-geology, biocolo, nishinoshima-gateway-production, crime, disease, noise, traffic, celestora, orbitalio, perks"
    • Changedsearch_apis1 field changed
      • changedInput schema / properties / domain / description
        Previous value: -"Filter by domain: cultural, earth, energy-calc, green-path, harmonias, hydrogen, internal, nanosnap, natura, platform, sakurahub, science, sim, social, space, stocks"New value: +"Filter by domain: cultural, earth, energy-calc, green-path, harmonias, hydrogen, internal, nanobase, nanosnap, natura, platform, sakurahub, science, sim, social, space, stocks"
  6. 1 tool update
    • Changedexecute_api1 field changed
      • changedInput schema / properties / api / description
        Previous value: -"API name: artia, marketo, atmos, chronomap, hydros, lithos, terra, carbon-credit, cost-compare, demand-forecast, grid-connect, site-matching, storage-optimize, tariff-optimize, transmission-loss, carbonias, planetary, green-path-api, biomassia, gasturbia, geothermia, hydria, reactoria, renewio, solaria, windaria-api, hydrogen, sla-viewer-production, nanobase-api, nanobase-console, nanosnap-auction-production, nanosnap-console, nanosnap-gacha-production, nanosnap-inventory-production, nanosnap-leaderboard-production, nanosnap-mailbox-production, nanosnap-persona-gateway-production, nanosnap-presence-production, nanosnap-replay-production, nanosnap-room-production, nanosnap-save-data-production, nanosnap-spatial-message-production, nanosnap-world-counter-production, nanosnap-world-objects-production, biositia, biota, cryonia, faunaunify, insectunify, literatia, plantunify, ppn-hub-workers, onokoro, sakurahub-address, sakurahub-gateway, sakurahub-web, weathio, biolexia-production, science-climate, science-ecology, science-geology, biocolo, crime, disease, noise, traffic, celestora, orbitalio, perks"New value: +"API name: artia, marketo, atmos, chronomap, hydros, lithos, terra, carbon-credit, cost-compare, demand-forecast, grid-connect, site-matching, storage-optimize, tariff-optimize, transmission-loss, carbonias, planetary, green-path-api, biomassia, gasturbia, geothermia, hydria, reactoria, renewio, solaria, windaria-api, hydrogen, sla-viewer-production, nanobase-api, nanobase-console, nanosnap-console, nanosnap-gacha-production, nanosnap-inventory-production, nanosnap-leaderboard-production, nanosnap-mailbox-production, nanosnap-persona-gateway-production, nanosnap-presence-production, nanosnap-replay-production, nanosnap-room-production, nanosnap-save-data-production, nanosnap-spatial-message-production, nanosnap-world-counter-production, nanosnap-world-objects-production, biositia, biota, cryonia, faunaunify, insectunify, literatia, plantunify, ppn-hub-workers, onokoro, sakurahub-address, sakurahub-gateway, sakurahub-web, weathio, biolexia-production, science-climate, science-ecology, science-geology, biocolo, nishinoshima-gateway-production, crime, disease, noise, traffic, celestora, orbitalio, perks"
  7. 1 tool update
    • Changedexecute_api1 field changed
      • changedInput schema / properties / api / description
        Previous value: -"API name: artia, marketo, atmos, chronomap, earth-geodata, hydros, lithos, terra, carbon-credit, cost-compare, demand-forecast, grid-connect, site-matching, storage-optimize, tariff-optimize, transmission-loss, carbonias, planetary, green-path-api, biomassia, gasturbia, geothermia, hydria, reactoria, renewio, solaria, windaria-api, hydrogen, sla-viewer-production, nanobase-api, nanobase-console, nanosnap-auction-production, nanosnap-console, nanosnap-gacha-production, nanosnap-inventory-production, nanosnap-leaderboard-production, nanosnap-mailbox-production, nanosnap-persona-gateway-production, nanosnap-presence-production, nanosnap-replay-production, nanosnap-room-production, nanosnap-save-data-production, nanosnap-spatial-message-production, nanosnap-world-counter-production, nanosnap-world-objects-production, biositia, biota, cryonia, faunaunify, insectunify, literatia, plantunify, ppn-hub-workers, onokoro, sakurahub-address, sakurahub-gateway, sakurahub-web, weathio, biolexia-production, science-climate, science-ecology, science-geology, biocolo, crime, disease, noise, traffic, celestora, orbitalio, perks"New value: +"API name: artia, marketo, atmos, chronomap, hydros, lithos, terra, carbon-credit, cost-compare, demand-forecast, grid-connect, site-matching, storage-optimize, tariff-optimize, transmission-loss, carbonias, planetary, green-path-api, biomassia, gasturbia, geothermia, hydria, reactoria, renewio, solaria, windaria-api, hydrogen, sla-viewer-production, nanobase-api, nanobase-console, nanosnap-auction-production, nanosnap-console, nanosnap-gacha-production, nanosnap-inventory-production, nanosnap-leaderboard-production, nanosnap-mailbox-production, nanosnap-persona-gateway-production, nanosnap-presence-production, nanosnap-replay-production, nanosnap-room-production, nanosnap-save-data-production, nanosnap-spatial-message-production, nanosnap-world-counter-production, nanosnap-world-objects-production, biositia, biota, cryonia, faunaunify, insectunify, literatia, plantunify, ppn-hub-workers, onokoro, sakurahub-address, sakurahub-gateway, sakurahub-web, weathio, biolexia-production, science-climate, science-ecology, science-geology, biocolo, crime, disease, noise, traffic, celestora, orbitalio, perks"
  8. 2 tool updates
    • Changedexecute_api1 field changed
      • changedInput schema / properties / api / description
        Previous value: -"API name: artia, craftia, festivia, marketo, atmos, chronomap, earth-geodata, hydros, lithos, terra, carbon-credit, cost-compare, demand-forecast, grid-connect, site-matching, storage-optimize, tariff-optimize, transmission-loss, carbonias, laboria, planetary, green-path-api, biomassia, gasturbia, geothermia, hydria, reactoria, renewio, solaria, windaria-api, hydrogen, sla-viewer-production, nanobase-api, nanobase-console, nanosnap-auction-production, nanosnap-console, nanosnap-gacha-production, nanosnap-inventory-production, nanosnap-leaderboard-production, nanosnap-mailbox-production, nanosnap-persona-gateway-production, nanosnap-presence-production, nanosnap-replay-production, nanosnap-room-production, nanosnap-save-data-production, nanosnap-spatial-message-production, nanosnap-world-counter-production, nanosnap-world-objects-production, biositia, biota, cryonia, faunaunify, insectunify, literatia, mineral, plantunify, ppn-hub-workers, amenity-production, onokoro, sakurahub-address, sakurahub-gateway, sakurahub-web, weathio, biolexia-production, science-climate, science-ecology, science-geology, biocolo, crime, disease, noise, traffic, celestora, orbitalio, perks"New value: +"API name: artia, marketo, atmos, chronomap, earth-geodata, hydros, lithos, terra, carbon-credit, cost-compare, demand-forecast, grid-connect, site-matching, storage-optimize, tariff-optimize, transmission-loss, carbonias, planetary, green-path-api, biomassia, gasturbia, geothermia, hydria, reactoria, renewio, solaria, windaria-api, hydrogen, sla-viewer-production, nanobase-api, nanobase-console, nanosnap-auction-production, nanosnap-console, nanosnap-gacha-production, nanosnap-inventory-production, nanosnap-leaderboard-production, nanosnap-mailbox-production, nanosnap-persona-gateway-production, nanosnap-presence-production, nanosnap-replay-production, nanosnap-room-production, nanosnap-save-data-production, nanosnap-spatial-message-production, nanosnap-world-counter-production, nanosnap-world-objects-production, biositia, biota, cryonia, faunaunify, insectunify, literatia, plantunify, ppn-hub-workers, onokoro, sakurahub-address, sakurahub-gateway, sakurahub-web, weathio, biolexia-production, science-climate, science-ecology, science-geology, biocolo, crime, disease, noise, traffic, celestora, orbitalio, perks"
    • Changedsearch_apis1 field changed
      • changedInput schema / properties / domain / description
        Previous value: -"Filter by domain: cultural, earth, energy-calc, esg, green-path, harmonias, hydrogen, internal, nanosnap, natura, platform, sakurahub, science, sim, social, space, stocks"New value: +"Filter by domain: cultural, earth, energy-calc, green-path, harmonias, hydrogen, internal, nanosnap, natura, platform, sakurahub, science, sim, social, space, stocks"
  9. 1 tool update
    • Changedsearch_apis1 field changed
      • addedInput schema / properties / region
        Added value: +{
+  "description": "Filter by ISO 3166-1 alpha-2 region the API serves data for (e.g. \"JP\"). Returns region-specific + global APIs; excludes APIs limited to other regions.",
+  "maxLength": 2,
+  "minLength": 2,
+  "type": "string"
+}
  10. 3 tool updates
    • First observedenvironment_brief
    • First observedexecute_api
    • First observedsearch_apis

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources