"A tool to manage and process a list of Swagger API endpoints" matching MCP tools:

• call_dpf_apiA

  mcp-serverA

  Escape hatch for DPF capabilities that don't have a dedicated tool yet. ALWAYS prefer a dedicated tool when one exists — get_status, list_data, submit_query, delete_data_spec, onboard_data_source, update_data_spec, run_data_job, manage_connection, manage_trigger, setup_scheduled_pull, list_my_workspaces, create_workspace — and reach for this only when none of those fit (e.g. "how many credits do I have?" -> path "/auth/billing", action "get-balance"; a brand-new action added to the API since this server's tools were last updated). Every DPF endpoint is POST <path> with a JSON body of { action, ...fields }, authenticated with your OAuth session automatically. Pass workspaceId explicitly for workspace-scoped actions (data-specs, connections, job-triggers, and under "/workspaces": get-workspace, list-queries, list-bytes-accessed, list-storage, list-processed-files, list-trigger-runs) — omit it entirely for account-level actions that reject one (under "/workspaces": create, get-workspaces, grant-permission, revoke-permission, update/delete-workspace; under "/auth/billing": get-balance only — billing mutations such as purchase-credits, modify-subscription, manage-payment, and create-customer are NOT available via MCP; direct the user to https://dpf-it.com/workspace.html#credits for all credit and subscription management). If unsure of an action's exact fields, read the "dpf-openapi-spec" resource (dpf://openapi/spec.yaml) rather than guessing. Exception: the raw Iceberg REST proxy under "/iceberg/v1/..." (e.g. to read or set a table's "dpf.primary-keys" property via a commit-table request) does not use the action convention at all — give action any placeholder string (it's ignored) and put the real Iceberg REST commit body, e.g. {"requirements":[],"updates":[{"action":"set-properties","updates":{"dpf.primary-keys":"col_a,col_b"}}]}, in params. This tool only issues POST, so Iceberg's GET-based reads (loadTable, listTables) aren't reachable this way. Returns the raw response data (or, for endpoints like the Iceberg proxy with no {success, data} envelope, the whole response body).

  Connector

  Destructive

  OAuth

• list_schemasA

  RoutebaseA

  List all schemas of an API specification. Optionally include usage counts showing how many endpoints reference each schema. Set scope to 'project' to look across every spec in the project instead — that returns the groups of structurally identical schemas (candidates for the shared library) plus counts, not the full list, and specId is then ignored. Every entry carries the rowVersion update_schema needs, so a batch of updates does not need a get_schema per schema first. Use this to browse schemas or find a schema id; for one schema with its full definition use get_schema. Requires project context.

  ConnectorAPI key

• list_endpointsA

  nordic-dataA

  Discovery meta-tool. Lists ALL available Nordic Data API data endpoints (HTTP method, path, short description) by reading the backend's live OpenAPI spec at runtime — far beyond the curated high-level tools. Use this to discover capabilities the dedicated tools do not cover, then call get_endpoint_schema for parameter details and call_endpoint to execute one. Only read-only operations are listed (GET/HEAD plus the POST screening queries); admin and state-changing endpoints are never returned. Supports an optional `search` keyword filter. The catalog has 230+ endpoints.

  ConnectorNo auth

• switch_active_companyA

  doolaA

  Point the formation tools at a different company the customer already owns. Use when the customer asks to manage / continue / inspect a specific company by name or ID. The companyId must come from `list_companies` — unknown IDs are rejected. After switching, the response carries the same shape as `get_company_onboarding_status` for the new active company, so the agent knows immediately which step to resume from. The override is process-local; if the customer reconnects and ends up on a different MCP replica, just call this tool again.

  ConnectorOAuth

• etfsA

  TwelvedataA

  Twelve Data reference list of supported ETF symbols (64,000+ listings worldwide) with exchange and country metadata — paged, default 200 rows, `count` is the total matched. Filter by symbol (e.g. "SPY"), country or exchange. Use to discover or validate ETF tickers before querying price endpoints. A stock ticker (e.g. "AAPL") is not an ETF and returns an empty list with `empty_reason: wrong_instrument_class` — use the stocks tool for those.

  ConnectorNo auth

• search_endpointsA

  PerceptlayerA

  Find Perceptlayer endpoints for a website or kind of data. The catalogue has 1659 endpoints across 248 sources, so search before calling. Query with the site and the data you want, e.g. "amazon product reviews", "airbnb listing", "linkedin company", "google maps places", "zillow property". Returns compact matches: endpoint ID (pass it to get_endpoint or call_endpoint), name, HTTP method, credits per call, tier ("restricted" endpoints need the account's restricted-endpoint terms accepted) and required parameters. Free; no API key needed.

  ConnectorNo auth

• save_whatsapp_toolA

  ErzyCallA

  Add or edit non-secret configuration for a WhatsApp HTTP, remote MCP, platform or connected-app tool after confirming the exact change. Pass id to edit and complete configuration; omit url to preserve an existing endpoint. Input schema must describe an object. This customer MCP schema rejects credentials; manage authentication headers in dashboard settings or through the REST API. Creating a tool does not enable it; assign IDs using update_whatsapp_agent updates.externalToolIds. Reuse the same idempotencyKey on retries. Requires whatsapp_agents:write.

  ConnectorOAuth

• find_api_endpointsA

  NetActuateA

  Searches the documentation of NetActuate's API (the API reference at netactuate.com/docs) for endpoints by what they do: 'create a virtual machine', 'list BGP sessions', 'firewall rules', 'DNS records', 'Kubernetes cluster'. It only reads that documentation: it never calls NetActuate's API and cannot change anything. Every word must match (filler such as 'a' or 'API' is ignored), read in the API's own terms ('VM' finds cloud server endpoints first, 'create' finds build ones), and the verb weighs the documented method; with no query it lists endpoints `limit` at a time. Each result gives the documented HTTP method, path, one-line summary, API version (v2 or v3; both are current, v3 for the newer resources) and the URL of its reference page, where the parameters and request body are; count is the full number of matches. Use for 'how do I do X with the NetActuate API'. For how-to guides, Terraform and Ansible: search_netactuate or get_netactuate_doc.

  ConnectorNo auth

• adcritter_build_appA

  AdCritter for BuildersA

  Start here when building an application. Returns an overview of what the AdCritter platform offers and a catalog of feature guides you can query with the adcritter_guidance tool to learn how to build each part of the app. Call adcritter_guidance(key) for any feature area to get detailed building instructions with API endpoints and response shapes.

  ConnectorNo auth

• get_endpoint_schemaA

  nordic-dataA

  Discovery meta-tool. Returns the full parameter and response schema for a single Nordic Data API endpoint (path + method), read from the backend's live OpenAPI spec with $refs resolved inline. Use after list_endpoints to learn exactly which parameters an endpoint takes before calling it with call_endpoint. Admin endpoints are rejected.

  ConnectorNo auth

• factreason_api_schemaA

  FactGrid (Renamed to FactReason)A

  Search exact request and response schemas for third-party API endpoints. Pass service alone to list its indexed endpoints, add query to narrow by path or operation, or use query alone across services; returns matches or nearest services. Uses metered access and does not modify source data. Prefer factreason_integration_brief for one callable request.

  ConnectorNo auth

• factreason_api_schemaA

  FactReasonA

  Search exact request and response schemas for third-party API endpoints. Pass service alone to list its indexed endpoints, add query to narrow by path or operation, or use query alone across services; returns matches or nearest services. Uses metered access and does not modify source data. Prefer factreason_integration_brief for one callable request.

  ConnectorNo auth

• get_api_specA

  algoum-mcpA

  Returns the OpenAPI specification of the algoum API as JSON: all endpoints and parameters, response and error schemas, pagination, timestamps and rate limit. Call it when a tool's description is not enough, for example to look up a response field or an error code.

  ConnectorAPI key

• import_api_endpointsA

  NebelusA

  Import custom API endpoints in bulk from a Postman collection (v2.x), an OpenAPI 3 / Swagger 2 spec, or endpoint JSON. Preview with dry_run=true (default), then import with dry_run=false; agent_id also attaches each one. Secret auth values in the source are stripped (listed in needs_auth) — complete auth in the portal or via set_endpoint_auth. Existing endpoint names are skipped, so re-importing is safe.

  ConnectorAPI key

• list_endpointsA

  Trillboards DOOH AdvertisingB

  List every registered Trillboards API operation. WHEN TO USE: - First call in an agent session to learn what the API offers. - Filter to agent_safe=true to list only side-effect-free endpoints. - Narrow to a single surface (data-api, sdk-api, device-api, sensing-api, partner-api-generated, dsp-api-generated). RETURNS: - operations: Array of { surface, method, path, operation_id, summary, description, agent_safe, idempotent, cost_tier, tags, doc_url, example_request } - total_operations: Total count. - surfaces: Known surface identifiers. EXAMPLE: Agent: "What read-only endpoints can I call?" list_endpoints({ agent_safe: true })

  ConnectorNo auth

• directiq_write_requestA

  DirectIQA

  Issue an authenticated POST, PUT, PATCH, or DELETE request to any DirectIQ endpoint. May create, modify, or permanently delete account data, including bulk operations. Prefer a dedicated directiq_* tool when one exists; use this only for operations without one, found with directiq_list_endpoints, and confirm destructive calls with the user first. Full request/response schemas for each group are in the DirectIQ API docs at https://rest.directiq.com/{group}/swagger/index.html (core, contacts, subscription).

  Connector

  Destructive

  No auth

• get_apiA

  Apis GuruA

  Get the full directory entry for one API by its exact APIs.guru name/key (e.g. "stripe.com" or "googleapis.com:calendar"). Returns every version of that API with its info (title, description, provider, categories), last-updated date, docs link, and OpenAPI/Swagger spec URLs (swaggerUrl JSON + swaggerYamlUrl YAML), plus which version is preferred. Use this once you know the exact name (from search_apis) to fetch the spec URLs for an API.

  ConnectorNo auth

• search_nolio_api_docsA

  NolioA

  Find the best tool for a task — curated tools first, raw API paths below. Ranks the curated tools and the raw OpenAPI endpoints for your keywords together. A `curated` result names a tool: call it directly (it carries the right defaults and guardrails). A `raw` result gives a `/api/v2` path to reach with the `call_with` generic tool (`nolio_api_read` / `nolio_api_write`); pass it to get_endpoint_schema for its exact shape. A raw route a curated tool already covers never appears — its tool surfaces instead. `query` may be one or several keywords, e.g. 'records', 'hrv metric', 'plan a workout'.

  ConnectorOAuth

• resolve_aliasA

  dns-of-moneyA

  Resolve a human-readable financial alias (pay: address) to payment endpoints and routing metadata. Call this before initiating any payment to a pay: address. Returns the preferred rail, fallback endpoints, an ISO 20022 hint, and a compliance signal. Anonymous calls return status only; a free API key (no credit card) unlocks the endpoint set — which rails and currencies the alias accepts — via POST /api/v1/access-requests. You do NOT need a key to pay: get_payment_requirements returns a payable address to any caller. Example: resolve_alias('pay:acme.user').

  ConnectorNo auth

• list_request_body_componentsA

  RoutebaseA

  List all reusable request body components (OpenAPI components/requestBodies) of an API specification. Optionally include usage counts showing how many endpoints link each component. Use this to browse or find an id; for one component with its schema use get_request_body_component. Requires project context.

  ConnectorAPI key

• fetch_campaignsA

  Sweeppea MCPA

  List the account email and SMS campaigns, newest first, with filters and pagination. Defaults to 25 per page, maximum 100. Campaigns CANNOT be created through this API — this MCP can only read them, pause, resume and cancel. The API leaves campaign creation out on purpose (confirmed by the API maintainer, October 2026), so it is a deliberate boundary rather than a gap waiting to be filled. Email templates and sender profiles have no endpoints at all, for the same reason. If the user wants a new campaign, say so plainly and point them at the Sweeppea app; do not pretend a tool exists and do not propose one. Read-only and NOT gated by the Send Message module: only the writes of this category document a module-not-enabled 403. If this call returns 403, look for another cause before telling the user the module is off.

  ConnectorNo auth