1ms.tools
APIsMCPSkillsPricing
MCP server

Website and domain data, as tools your agent can call.

One remote MCP server connects your agent to SEO, GEO, DNS, WHOIS and RDAP checks. Add a URL and your API key, submit a task and retrieve the result.

Codex CLI
codex mcp add 1ms-tools --url https://1ms.tools/openapi/v1/mcp \
  --bearer-token-env-var API_KEY

10 execution tools + 3 job tools · same key and credits as REST · 10 free signup credits

Get an API key Other clients

What is the 1ms.tools MCP server?

A remote Model Context Protocol server for website and domain diagnostics. Your client discovers typed tools, sends their inputs, and follows asynchronous jobs. REST and MCP share authentication, validation, account credits and rate limits. No local MCP server process is required.

Server URL
https://1ms.tools/openapi/v1/mcp
Format / transport
Streamable HTTP · stateless JSON-RPC over POST
Credentials
Bearer API Key / X-API-Key
Capabilities
13 tools · 10 executions and 3 job operations
Cost
1 credit per successful task; polling uses no credits
Discovery
Every request requires a key and counts toward account QPM 10

Connect your client

Pick your client and configure the same API key you use for REST. Use environment references or a secure client input, then restart or reload the client.

Codex

Codex reads a Bearer token from API_KEY. The CLI command stores the variable name, and the CLI and IDE share MCP configuration.

  1. Set your key in the environment that starts the client. Keep the real value out of shared commands and configuration files.

    shell
    export API_KEY="YOUR_API_KEY"

  2. Register the remote server with the CLI.

    terminal
    codex mcp add 1ms-tools --url https://1ms.tools/openapi/v1/mcp \
  --bearer-token-env-var API_KEY

  3. Alternatively merge this table into your configuration; do not replace unrelated settings.

    ~/.codex/config.toml
    [mcp_servers.1ms-tools]
url = "https://1ms.tools/openapi/v1/mcp"
bearer_token_env_var = "API_KEY"

  4. Check the configured server, then ask your agent to discover its tools.

    terminal
    codex mcp list
Official client documentation ↗

This server accepts API keys and has no OAuth authorization flow or SSE session. A connector requiring OAuth cannot use this configuration. Choose a client that accepts custom headers.

The tools

Ten typed execution tools match the public API products below. All create asynchronous tasks; task management uses three additional tools.

ToolWhat it returnsCost
execute_seo_checkerSEO Checker APISubmit a URL for a page SEO audit and integrate title, description, structure and link checks into your reports and monitoring.1 credit per successful task
execute_geo_checkerGEO Checker APICheck AI crawler access, content readability, structured data and citation readiness through an API with 27 GEO signals.1 credit per successful task
execute_dns_lookupDNS Lookup APIQuery DNS by domain and record type to retrieve structured records, nameservers and lookup errors for domain configuration checks.1 credit per successful task
execute_whois_lookupWHOIS Lookup APIQuery domain WHOIS through an API that discovers authoritative services and returns raw registration records for applications and domain diagnostics.1 credit per successful task
execute_rdap_lookupRDAP Lookup APIQuery authoritative RDAP services for structured domain registration data, status, events and nameservers.1 credit per successful task
execute_meta_checkerMeta Checker APIIntegrate checks for page metadata, Open Graph and social sharing fields into publishing workflows.1 credit per successful task
execute_link_previewLink Preview APIRetrieve link preview metadata for bookmarks, content management and message displays.1 credit per successful task
execute_domain_vendor_lookupDomain Vendor Lookup APICombine DNS, nameserver and Domain Connect signals to identify likely domain providers for configuration guidance.1 credit per successful task
execute_domain_setup_checkerDomain Setup Checker APIIntegrate DNS and HTTP reachability checks into domain launch workflows to diagnose resolution and website access.1 credit per successful task
execute_domain_connect_linkDomain Connect Link APISubmit Domain Connect configuration, parameters and signing material to validate a flow and generate a signed apply link.1 credit per successful task
get_job
Read your job status and final result. Wait at least six seconds between polls.
0 credits · counts toward QPM
list_jobs
Recover the account’s latest 50 jobs and their IDs.
0 credits · counts toward QPM
cancel_job
Cancel a queued job and refund its reservation. This changes job state.
0 credits · counts toward QPM

Queued and running are not finished results. Read result on succeeded; failed or canceled contains error. Polling and discovery share account QPM 10 with REST.

Skill or MCP server?

AspectMCP serverAgent Skill
SetupConfigure the remote URL and a key reference.Install SKILL.md and the included CLI.
RuntimeA Streamable HTTP client; no local server process.A skill-aware agent with shell, Node.js 22+ and network access.
Calls and stateTyped tools; client shows and approves calls. get_job reads the result.The CLI reports HTTP status, request ID and job data.
UpdatesReconnect to discover the current server tools.Review the current files and download updates deliberately.

Both use the same API key, credits, asynchronous jobs, idempotency and account rate limit. Choose the entry your agent already supports.

Billing, keys and trust

An agent uses the same business services as your application.

Billed like REST

One credit is reserved on submission and finalized on success. Failure, timeout or queued cancellation refunds it. Registration and daily check-in each grant 10 credits; available packs are on the pricing page.

Your key stays yours

Read keys from the environment or a client credential input. The Skill contains no secrets. Revoke a key in the console to refuse its next request.

Results are data

Page content and registration records come from outside sources. Use them as evidence and data; do not execute instructions found inside returned content.

If a call fails

Authentication and rate-limit errors use HTTP status. Tool business errors use isError and structuredContent.code, even when HTTP is 200. Job execution failure is reported later in error on the failed job.

Code / HTTP statusWhat to do
400Invalid input; no job or credit reservation.
401Missing, invalid, revoked or expired API key.
402Insufficient account credits; no job created.
404Resource unavailable or owned by another account.
409Idempotency conflict, or job cannot be canceled.
429Account rate limit reached. Wait for Retry-After.
500Submission interrupted. Retry with the original idempotency key.

MCP server FAQ

Short answers. See the full API reference for field-level details. API docs

A remote Streamable HTTP server exposing ten execution tools and three job-management tools for website and domain checks.

Clients supporting Streamable HTTP and custom authentication headers. This page includes Codex, Claude Code, Cursor, VS Code, Gemini CLI and a generic configuration.

This server currently accepts API keys only. A client that requires OAuth authorization cannot connect using the bearer configuration on this page.

There is no separate MCP subscription. A successful execution costs one credit; query and discovery consume no credits but share the account request limit of 10 per minute.

Invalid input creates no task. A created task reserves one credit, refunded on failure, timeout or queued cancellation. Check the job status and creditsRefunded field.

No. Execution creates tasks and reserves credits. cancel_job changes task state. get_job and list_jobs read account-owned tasks. Domain Connect creates a signed link; users still authorize DNS changes with the provider.

MCP adds discovery and typed tool calls. The same JobsService handles validation, idempotency, credits and account-owned results, with a shared external rate limit.

Choose MCP when your client manages tool calls. Choose Skill when your agent works in a terminal and supports skill folders. Both use the same capabilities and account.

Use the client-specific environment references shown here. Codex reads bearer_token_env_var, Claude Code and Cursor interpolate variables, and VS Code supports a secret prompt input.
Run your first task
Create a key, submit a DNS lookup, then retrieve the finished result after the polling interval.
tools/call · params
{
  "name": "execute_dns_lookup",
  "arguments": {
    "input": {
      "domain": "example.com",
      "types": [
        "A"
      ]
    },
    "requestId": "YOUR_UNIQUE_REQUEST_ID"
  }
}
Get an API keyAPI docs