MCP servers › com.trygoppa › goppa
MCP server · registry snapshot 2026-10-30 · last tested 2026-10-30
goppa MCP server
Registry name com.trygoppa/goppa
by trygoppa.com · domain (the registry's namespace rule)Website ↗
See whether ChatGPT, Google AI and Perplexity name your business, and get the fixes applied. — the publisher's description
Summary
com.trygoppa/goppa is a remote MCP server listed in the official MCP registry at version 1.0.0, under the namespace of the domain trygoppa.com. On 2026-10-30 ProtocolProbe connected to it in read-only mode and read its inventory: 24 tools, 1 resource and 5 prompts.
Record checks
1 of 2 record checks met · 7 do not apply
- met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason
Operate this server? Correct a fact · README badge · Run the checks yourself
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Tools
- 24
- Last tested
- 2026-10-30
Tool list size
6,290 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (24 tools). Counted with Anthropic's token counter on 2026-10-30, from the tool list we read on 2026-10-30. Median across 25,738 counted servers: 2,858 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-10-30 (trygoppa.com), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (1.0.0).
Observed fact
This server accepted a session without any credential and lists 1 tool whose name or declaration suggests it changes data (add_site). That is our reading of the names; we did not call it. Source: our connection, 2026-10-30.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-30
- Mode
- read-only (no tool calls)
- Latest version
- 1.0.0, published 2026-10-29 (registry, as of the 2026-10-30 snapshot)
- First listed version
- 2026-10-29 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-10-30
- Package and repository
- checked 2026-10-30
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
New in the registry: not in the list of 2026-10-29, listed on 2026-10-30 with version 1.0.0 (published 2026-10-29).
Source: the official MCP Registry list on 2026-10-29 and on 2026-10-30.
What it is
What does this server offer?
Observed inventoryNone of its 24 tools are described as changing anything. For 24 the reading was uncertain, so no mark is shown.
- get_accounton 123 other servers
“Your Goppa account: plan, sites, AI measurements used and left this month (and in total, where the account has a total), keyword research left, the next scheduled AI measurement and the next automati…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
sitestring“Optional: one of your sites in Goppa, by domain (example.com), to also read that site's measurement schedule, automatic check and keyword research.”cursorstring“next_cursor from the previous page, to read the next 10 items.”
- get_ai_visibilityon 4 other servers
“Whether AI assistants named your site in the latest Goppa measurement, one engine at a time (ChatGPT, Gemini, Google AI Overview, Google AI Mode, Perplexity): named in k of n answers, the market and …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
sitestring“One of your sites in Goppa, by domain (example.com).”
- get_what_changed
“What changed between the two latest comparable measurements, with a paired test over the same questions and engines: pairs gained, pairs lost, and whether the change is real or within normal ups and …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs
sitestring“One of your sites in Goppa, by domain (example.com).”cursorstring“next_cursor from gained_pairs.page or lost_pairs.page, to read the next 10 of that list (the other list starts again from its first page).”gained_cursorstring“next_cursor from gained_pairs.page, to read the next 10 gained pairs.”lost_cursorstring“next_cursor from lost_pairs.page, to read the next 10 lost pairs.”
- get_weekly_summaryon 4 other servers
“A weekly summary of one site: what changed in AI answers since the previous comparable measurement, engine by engine (named in k of n answers, with a paired test); Google alerts (rankings, pages, rob…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
sitestring“One of your sites in Goppa, by domain (example.com).”
- get_competitorson 10 other servers
“Businesses AI assistants named in the same answers as your site, engine by engine: named in k of n answers, and how many answers named them and not you.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
sitestring“One of your sites in Goppa, by domain (example.com).”cursorstring“next_cursor from the previous page, to read the next 10 items.”
- get_ai_sources
“The sites AI assistants cited when answering your questions, engine by engine, and in how many of those answers you were named.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
sitestring“One of your sites in Goppa, by domain (example.com).”cursorstring“next_cursor from the previous page, to read the next 10 items.”
- get_ai_answers
“The answers recorded in the latest measurement: the question, the engine, whether you were named or cited, the businesses and sources in it, and an excerpt of the answer.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
sitestring“One of your sites in Goppa, by domain (example.com).”cursorstring“next_cursor from the previous page, to read the next 10 items.”enginestring“Only the answers of this engine.”
- get_next_stepson 1 other server
“Your next open step in the Goppa guide and the five after it: what to do, why, the steps, and where to see the effect.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
sitestring“One of your sites in Goppa, by domain (example.com).”
- get_site_check
“The latest AI readability check of your site: checks passed (k of n), the score, and how to fix each failing check.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
sitestring“One of your sites in Goppa, by domain (example.com).”cursorstring“next_cursor from the previous page, to read the next 10 items.”
- get_ai_trafficon 2 other servers
“Real AI use counted on your own site by the Goppa plugin: pages an assistant opened to answer a person, clicks from inside AI answers, and crawler visits, kept separate and never added together.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
sitestring“One of your sites in Goppa, by domain (example.com).”cursorstring“next_cursor from the previous page, to read the next 10 items.”
- get_google_rankings
“Your tracked Google searches: the position range (Top 3, 4-10, 11-20, 21-30, not in top 30), the change since the last check, monthly searches, and ranking alerts.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
sitestring“One of your sites in Goppa, by domain (example.com).”cursorstring“next_cursor from the previous page, to read the next 10 items.”
- get_site_auditon 2 other servers
“Your page-by-page site audit: pages without errors (k of n), each problem with how many pages have it and why it matters, and what changed since the previous audit.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
sitestring“One of your sites in Goppa, by domain (example.com).”cursorstring“next_cursor from the previous page, to read the next 10 items.”
Show 12 more tools
- get_google_overview
“Your site on Google and Bing beyond rankings: Search Console clicks and impressions over the last 28 days with the top searches and pages, the pages in Google's index, Bing clicks, the visibility ind…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
sitestring“One of your sites in Goppa, by domain (example.com).”
- get_keyword_ideas
“Your latest Google keyword research: quick wins (searches where you already rank 4 to 20), keyword ideas with monthly searches, difficulty and intent, the research left this month, and the keyword ga…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
sitestring“One of your sites in Goppa, by domain (example.com).”cursorstring“next_cursor from the previous page, to read the next 10 items.”
- get_google_competitors
“The sites that rank on Google for the most of the same searches as you: keywords in common, their size, and in how many of your tracked keywords they rank above you.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
sitestring“One of your sites in Goppa, by domain (example.com).”
- get_backlinkson 3 other servers
“The sites that link to yours: linking sites, backlinks and broken backlinks, new and lost month by month, and the link gap: sites that link to your Google competitors and not to you.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
sitestring“One of your sites in Goppa, by domain (example.com).”
- get_seo_fixes
“The SEO fixes Goppa prepared for your pages (titles, meta descriptions, image text): the ones waiting for your approval with the current and proposed text, the ones applied on your site, and the prod…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
sitestring“One of your sites in Goppa, by domain (example.com).”cursorstring“next_cursor from the previous page, to read the next 10 items.”
- run_site_check
“Run a new AI readability check on one of your sites now and save it to your Goppa account.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
1 input
sitestring“One of your sites in Goppa, by domain (example.com).”
- add_siteon 7 other servers
“Add one of your websites to your Goppa account, so Goppa can check, measure and track it.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
1 input, 1 required
sitestringrequired“The website address to add, like yourstore.com.”
- run_ai_measurement
“Measure whether AI assistants (ChatGPT, Gemini, Google AI Overview, Google AI Mode, Perplexity) name one of your sites, with real answers.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
4 inputs
sitestring“One of your sites in Goppa, by domain (example.com).”marketstring“Where to ask, as a country code (uk, us, de, fr…) or a region (eu, global).”categoriesarray“The products or services to ask about, like 'running shoes' (3 to 35 characters each).”approvalstring“The approval code from the preview, sent only after the user agreed to the questions.”
- get_fixes_to_apply
“The SEO fixes the user already approved in Goppa for one site, ready to apply on the site with the tools you have there (the site's code, its builder or its own app): the page, the field (title, meta…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
sitestring“One of your sites in Goppa, by domain (example.com).”cursorstring“next_cursor from the previous page, to read the next 10 items.”include_site_filesboolean“Also suggest an llms.txt built from the pages Goppa read (default true).”
- report_fixes_applied
“Record in Goppa which approved SEO fixes from get_fixes_to_apply were applied on the site (applied), could not be applied (not_applied, with a reason), or were undone (undone, kept).”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
2 inputs
sitestring“One of your sites in Goppa, by domain (example.com).”resultsarray“One entry per fix handled, up to 50 per call.”
- scan_siteon 17 other servers
“Score any website 0-100 on how readable it is to AI assistants: crawler access, structured data, discovery files and agent protocols.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
urlstringrequired“Website address, e.g.”
- get_studyon 12 other servers
“Return findings from Goppa's 2026 Q3 study of 176 businesses that already rank on page one of Google: how many returned nothing to an identified crawler, which checks fail most, and how technical rea…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-30.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 100% of 43
- Tools with a description
- 100% of 24
- Typical description length
- 252 characters
The tool set
Counted from the listing
- Tools
- 24
- Size of the list
- about 17,544 tokens for an agent to load (characters ÷ 4)
- Naming
- 24 of 24 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 24 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-10-30 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://trygoppa.com/mcp/account
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"goppa": {
"url": "https://trygoppa.com/mcp/account"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"goppa": {
"type": "http",
"url": "https://trygoppa.com/mcp/account"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"goppa","type":"http","url":"https://trygoppa.com/mcp/account"}'Claude Code
claude mcp add --transport http goppa https://trygoppa.com/mcp/account
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"goppa": {
"type": "streamableHttp",
"url": "https://trygoppa.com/mcp/account",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"goppa": {
"httpUrl": "https://trygoppa.com/mcp/account"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.goppa] url = "https://trygoppa.com/mcp/account"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"goppa": {
"url": "https://trygoppa.com/mcp/account"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://trygoppa.com/mcp/account --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint trygoppa.com/mcp/account | Session opened | matches | our test · 2026-10-30 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-10-30 |
Choosing
Record checks
Public records · not a safety rating1 of 2 record checks met · 7 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-30. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about com.trygoppa/goppa
Answered from the data aboveWho publishes com.trygoppa/goppa?
The registry ties the namespace com.trygoppa to the domain trygoppa.com; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.
Does com.trygoppa/goppa need an API key or sign-in?
It opened a session without any credential on 2026-10-30. The registry entry declares no required credential; no declaration is not a guarantee.
Has com.trygoppa/goppa been security tested?
Partly. 5 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Open without sign-in
It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: exercised
- Fake assistant turns: exercised
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: exercised
5 exercised11 not run (reason given)2 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised - 12Hidden content
audience-hidingChecks resources that hide content from the user.exercised - 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
Source: our own test, 2026-10-30, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 1,653 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 24 tools, 1 resource, 5 prompts.
- 10,557 msFinished: 5 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “com.trygoppa/goppa: MCP server record.” Data checked 2026-10-30. https://protocolprobe.com/mcp/servers/com.trygoppa/goppa
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/com.trygoppa/goppa)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology