Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

com.seoapi/perplexitybot

REMOTE · PERPLEXITYBOT.SEOAPI.COM · SCANNED AUG 3

Validate PerplexityBot IP addresses. Remote MCP validate_ip tool.

Available components

remote · perplexitybot.seoapi.com 61
+2 this week 61 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security54
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 61 tokens (~61/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · perplexitybot.seoapi.com

# add to Claude Code
claude mcp add --transport http com-seoapi-perplexitybot https://perplexitybot.seoapi.com/mcp
# ~/.codex/config.toml
[mcp_servers.com-seoapi-perplexitybot]
url = "https://perplexitybot.seoapi.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-seoapi-perplexitybot": {
      "type": "remote",
      "url": "https://perplexitybot.seoapi.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-seoapi-perplexitybot --url https://perplexitybot.seoapi.com/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-seoapi-perplexitybot:
    url: "https://perplexitybot.seoapi.com/mcp"
// mcp.json
{
  "mcpServers": {
    "com-seoapi-perplexitybot": {
      "type": "http",
      "url": "https://perplexitybot.seoapi.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Jul 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 27 Jul 26 +47
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 12

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://perplexitybot.seoapi.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=seoapi.com CN=WE1,O=Google Trust Services,C=US 15 Jul 2026 13 Oct 2026 ECDSA 256 ECDSA-SHA256 727596118f97c9ec0e235b6b515bf804
SANs: seoapi.com, perplexitybot.seoapi.com, *.perplexitybot.seoapi.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC secure

Validation of perplexitybot.seoapi.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
seoapi.com. present 2371 13 Verified
perplexitybot.seoapi.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options SAMEORIGIN
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://perplexitybot.seoapi.com/mcp Verified 200
http (plaintext) http://perplexitybot.seoapi.com/mcp Inconclusive 405
MCP tools — 1 exposed · ~61 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
validate_ip ~61

Check whether an IP address (IPv4 or IPv6) is a genuine PerplexityBot IP address, verified against PerplexityBot's published IP data on seoapi.com.

NameTypeReqDescription
ipstringyesThe IPv4 or IPv6 address to validate

No output schema declared.

No examples provided.