Proposal: add the 1ToolRing and API Indonesia MCP servers to the integration catalog

Open
#935 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript, json

Research direction

Read integrations/catalog.schema.json and a similar entry in integrations/catalog/ to confirm the required fields and connection options. Check the API Indonesia authorization header against the documented 401 challenge, then add and validate one catalog entry at a time and regenerate integrations/catalog-index.js with npm run build:integrations. Done when both entries pass the catalog checks and listIntegrationCatalog({mcp:true,oauth:true}) returns both ids; the issue proposes separate PRs, and the comment thread names an auth correction for API Indonesia.

Written by the indexing model from the issue text.

Description

priority:low ready-for-dev

Summary

Add two hosted Streamable HTTP MCP servers to the integration catalog, both made by Khaisa Studio:

1ToolRing (https://mcp.1toolring.com/mcp) — one API key and one prepaid balance for thousands of pay-per-call tools: web search, maps places, shopping prices, market data (stocks, crypto, FX), web pages, images. discover_tools and inspect_tool are free, the price is shown before every paid call, and failed calls are not charged.

API Indonesia (https://mcp.apiindonesia.id/mcp) — 84 tools over official-source Indonesian public data: regions down to villages and postal codes, region boundaries, public holidays and cuti bersama, prayer times, Hijri dates, schools, universities, hospitals, BMKG earthquakes and weather warnings, air quality, Bank Indonesia exchange rates, minimum wage, NIK/NPWP format checks, QRIS parsing, and more. Sign-up includes 3,000 free credits and failed requests are not billed.

Motivation

The catalog already covers web search (Exa, Tavily, Brave Search) but nothing that bundles many third-party data providers behind one prepaid balance, and nothing for Indonesian public data. Both servers show the price of a call before it runs, so an agent can decide whether the call is worth it.

Proposed scope

  • Add integrations/catalog/1toolring.json: shttp transport, OAuth 2.1 with PKCE and dynamic client registration (clientAuthentication: "none"), plus an Authorization header option for an API key.
  • Add integrations/catalog/api-indonesia.json: same shttp + OAuth 2.1 (DCR) shape, plus an x-api-key header option.
  • Regenerate integrations/catalog-index.js with npm run build:integrations.
  • Two focused PRs, one per integration, once this issue is triaged.

Acceptance criteria

  • Both catalog/*.json files pass integrations/catalog.schema.json and the catalog sync test.
  • listIntegrationCatalog({mcp:true,oauth:true}) returns both ids.
  • The PRs show the live protected-resource metadata and the 401 challenge from each /mcp endpoint.

Notes

I work on both products. Live checks run today (2026-11-10):

  • GET https://mcp.1toolring.com/.well-known/oauth-protected-resource → 200, authorization_servers: ["https://app.1toolring.com"], scopes_supported: ["tools"].
  • GET https://mcp.apiindonesia.id/.well-known/oauth-protected-resource → 200, authorization_servers: ["https://mcp.apiindonesia.id"], scopes_supported: ["tools"].
  • An unauthenticated initialize POST to either /mcp endpoint returns 401 with a JSON-RPC error explaining both the OAuth and the API-key path.
  • https://1toolring.com/logo.svg and https://apiindonesia.id/favicon.svg resolve (200).

Both entries were drafted and validated locally (structure checked against every constraint in integrations/catalog.schema.json; npm run build:integrations regenerates the index cleanly). Draft JSON for review:

// integrations/catalog/1toolring.json
{
  "id": "1toolring",
  "name": "1ToolRing",
  "description": "Search the web, look up places, compare shopping prices, and read market data across thousands of pay-per-call tools billed from one prepaid balance.",
  "categories": ["Search", "Data & analytics"],
  "appUrl": "https://1toolring.com",
  "docsUrl": "https://docs.1toolring.com/overview/",
  "iconBg": "#2448FF",
  "logoUrl": "https://1toolring.com/logo.svg",
  "keywords": ["search", "web search", "maps", "places", "shopping", "prices", "market data", "stocks", "crypto", "web pages", "mcp"],
  "notes": "OAuth 2.1 with dynamic client registration and PKCE is the primary connection; a bearer API key works too. discover_tools and inspect_tool are free, the price is shown before every paid call, and failed calls are not charged.",
  "connectionOptions": [
    {
      "id": "oauth",
      "provider": "mcp",
      "transport": { "kind": "shttp", "url": "https://mcp.1toolring.com/mcp" },
      "auth": { "strategy": "oauth2", "oauth": { "clientAuthentication": "none" } }
    },
    {
      "id": "api",
      "provider": "mcp",
      "transport": {
        "kind": "shttp",
        "url": "https://mcp.1toolring.com/mcp",
        "headerFields": [
          {
            "key": "Authorization",
            "label": "1ToolRing API key",
            "type": "password",
            "required": true,
            "helperText": "Create a key in the 1ToolRing dashboard and paste it as `Bearer <key>`. Calls are billed from the account's prepaid balance.",
            "helperLink": "https://app.1toolring.com"
          }
        ]
      },
      "auth": { "strategy": "none" }
    }
  ]
}
// integrations/catalog/api-indonesia.json
{
  "id": "api-indonesia",
  "name": "API Indonesia",
  "description": "Look up Indonesian regions, postal codes, public holidays, prayer times, schools, hospitals, earthquakes, exchange rates, and other official public data.",
  "categories": ["Data & analytics", "Local & regional"],
  "appUrl": "https://apiindonesia.id",
  "docsUrl": "https://docs.apiindonesia.id",
  "iconBg": "#C8102E",
  "logoUrl": "https://apiindonesia.id/favicon.svg",
  "keywords": ["indonesia", "regions", "postal codes", "holidays", "prayer times", "schools", "hospitals", "earthquakes", "exchange rates", "public data", "mcp"],
  "notes": "84 tools over official-source Indonesian public data. Sign-in uses OAuth 2.1 with dynamic client registration and PKCE; an x-api-key header works too. Sign-up includes 3,000 free credits and failed requests are not billed.",
  "connectionOptions": [
    {
      "id": "oauth",
      "provider": "mcp",
      "transport": { "kind": "shttp", "url": "https://mcp.apiindonesia.id/mcp" },
      "auth": { "strategy": "oauth2", "oauth": { "clientAuthentication": "none" } }
    },
    {
      "id": "api",
      "provider": "mcp",
      "transport": {
        "kind": "shttp",
        "url": "https://mcp.apiindonesia.id/mcp",
        "headerFields": [
          {
            "key": "x-api-key",
            "label": "API Indonesia key",
            "type": "password",
            "required": true,
            "helperText": "Create a key in the API Indonesia dashboard. Sign-up includes 3,000 free credits and each successful request costs 2 credits.",
            "helperLink": "https://dashboard.apiindonesia.id"
          }
        ]
      },
      "auth": { "strategy": "none" }
    }
  ]
}

OpenHands AI triage

The following comments and acceptance criteria were added by the OpenHands AI agent.

Triage

Triage verdict: READY, prioritized priority:low. This is an additive catalog-data proposal in the repository's designated single-source directory (integrations/catalog/*.json), so no product design decision is required. Independently verified on 2026-11-10: both /.well-known/oauth-protected-resource endpoints return 200 with metadata matching the issue (authorization_servers, scopes_supported: ["tools"]); unauthenticated initialize POSTs to both /mcp endpoints return 401 with JSON-RPC errors naming the OAuth and API-key paths; the app, docs, and logo URLs resolve (200). Both draft entries were revalidated locally against integrations/catalog.schema.json (Draft 2020-12) and the structural rules in tests/test_catalogs.py (no-auth options must carry headerFields; password fields need helperText plus a helper link); both pass and both derive supportsMcp/supportsOauth as true.

One evidence-based adjustment to the proposed scope: the API Indonesia API-key option must collect the credential as the Authorization header (paste as Bearer <key>), not x-api-key. The server's own 401 message documents only Authorization: Bearer aip_live_xxx, and a live probe with an x-api-key header still returns "Missing API key" while an Authorization: Bearer header passes the auth stage. The 1ToolRing draft's Authorization header is correct as proposed. Keep the two focused PRs (one per integration) as proposed; each PR changes exactly one catalog JSON file plus the regenerated integrations/catalog-index.js (npm run build:integrations).

Non-goals: no SDK or Agent Canvas auth-surface changes, no automations/ changes, no icon assets under integrations/icons/, no aggregate catalog JSON or provider-specific runtime code (both prohibited by repo guidance), and no new guarantees about tool counts or pricing beyond the notes text the author already drafted.

priority:low because this is a well-formed but additive catalog proposal with no user reports, support evidence, or production impact recorded; per triage policy that keeps it at the default.

Acceptance Criteria
  • Each PR adds exactly one hand-authored file (integrations/catalog/1toolring.json in one PR, integrations/catalog/api-indonesia.json in the other) and modifies no other file under integrations/catalog/.
  • Both new entries validate against integrations/catalog.schema.json, and the catalog tests pass on the PR branch: uv sync --group test && uv run pytest -q tests/test_catalog_schema.py tests/test_catalogs.py tests/test_integration_catalog_in_sync.py.
  • integrations/catalog-index.js is regenerated with npm run build:integrations, and the PR diff shows only the new catalog file plus that generated index.
  • listIntegrationCatalog({mcp:true,oauth:true}) from @openhands/extensions/integrations returns both 1toolring and api-indonesia.
  • The api-indonesia API-key option collects the credential as the Authorization header with Bearer <key> helper text, and its PR evidence shows the server's 401 challenge documenting that path.
  • Each PR includes live evidence from the running services: the 200 oauth-protected-resource response and the unauthenticated 401 JSON-RPC challenge from the corresponding /mcp endpoint, plus HTTP 200 for the entry's docsUrl, appUrl, and logoUrl.
  • The catalog JSON and the PR contain no API keys, tokens, or credentials, and both password-type header fields keep non-empty helperText with an https helper link (enforced by test_credential_fields_have_helper_text_and_link).
Dominant language
Python
Stars
184
Forks
137
Avg merge
1d 19h
Merged PRs (30d)
46

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenHands/extensions

All issues in OpenHands/extensions

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.