MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

DomainKits

Earlier Revision Publisher unverified Confidence: Good (0.85)

DomainKits is an MCP server published by ABTdomain, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-25.

Does DomainKits support the current MCP specification (2026-07-28)?

Not yet confirmed. DomainKits is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-25.

Is DomainKits a first-party (official) MCP server?

Undetermined. We have not verified the publisher relationship for DomainKits (as of 2026-08-25).

How do I connect to DomainKits?

DomainKits is available via a hosted remote endpoint at https://api.domainkits.com/v1/mcp, the package npm:@domainkits/mcp, the official MCP Registry under io.github.ABTdomain/domainkits-mcp, the source repository at https://github.com/abtdomain/domainkits-mcp. Authentication: none. Transports: streamable-http.

What tools does DomainKits expose?

DomainKits exposes 32 tools, including active, aged, available, backlink_summary, bulk_available, bulk_tld (last verified 2026-08-25).

Does DomainKits support MCP revision 2025-11-25?

Yes. DomainKits supports MCP revision 2025-11-25 (checked 2026-08-25).

When were DomainKits's facts last verified?

2026-08-25. Each fact on this page links to the sources used to verify it.

Which tools does DomainKits expose?

32 tools verified.

  • active
  • aged
  • available
  • backlink_summary
  • bulk_available
  • bulk_tld
  • deleted
  • dns

Search newly registered, expired, aged, active, deleted and for-sale domains, plus WHOIS and DNS.

Which MCP spec revisions does DomainKits support?

DomainKits has 1 verified spec-support record. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.

Spec revision Status Last checked Evidence
MCP 2025-11-25 Supported Source

How widely adopted is DomainKits?

Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.

Repository and package signals for DomainKits

Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.

Repository as of

Stars
6
Forks
0
Last pushed
(39 days ago)
Created
Open issues
0
Continuous integration
None detected
Tests
None detected
Security policy
None

Declared topics: abtdomain, agentic-mcp, domain, domain-data-mcp, domain-intelligence, domain-mcp, domain-name-mcp, domain-search, domainkits, domains, mcp, model-context-protocol, nameserver, nameserver-reverse, newly-registered-domains, nrd, search-domain-name — author-declared on the repository, not our taxonomy.

Package (npm) as of

Latest version
2.1.1
Last published
First published
Releases
10
License (package)
MIT
Maintainers
1
Direct dependencies
0
Unpacked size
12 KB
Registry signature
Signed
Build provenance
No attestation

How was this verified, and what are the sources?

Verified · method: endpoint-probe · confidence 0.85 (Good).

  1. Official MCP Registry record for io.github.ABTdomain/domainkits-mcp at version 2.1.0 - lists remote endpoint https://api.domainkits.com/v1/mcp and repository https://github.com/abtdomain/domainkits-mcp - accessed
  2. Endpoint probe of https://api.domainkits.com/v1/mcp - declined server/discover; negotiated 2025-11-25 via the legacy initialize handshake; tools/list returned 28 tools - accessed
  3. Endpoint probe of https://api.domainkits.com/v1/mcp - declined server/discover; negotiated 2025-11-25 via the legacy initialize handshake; tools/list returned 32 tools - accessed