MCP servers › io.github.edvyno › akari-crypto-intel

MCP server · registry snapshot 2026-10-29 · last tested 2026-10-29

io.github.edvyno/akari-crypto-intel

by edvyno · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗

x402-paid crypto intel: HL funding, TradingView TA, wallet vetting, Polymarket edges. 19 tools. — the publisher's description

4 of 4 record checks metRead-only · tools listed 2026-10-29version 1.0.1Pythonstreamable HTTP23 tools

Summary

io.github.edvyno/akari-crypto-intel is a remote MCP server listed in the official MCP registry at version 1.0.1, under the namespace of the GitHub account edvyno. Its linked repository, github.com/edvyno/akari-x402-mcp, belongs to the same GitHub account. On 2026-10-29 ProtocolProbe connected to it in read-only mode and read its inventory: 23 tools, 0 resources and 0 prompts.

Record checks

4 of 4 record checks met · 4 do not apply · 1 not checked

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not checked: 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: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

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
Repository: public
Tools: 23
Last tested: 2026-10-29

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-10-29 (akari-x402.puzzling-marten.workers.dev), 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.1).

Add to your client

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-29

Mode

read-only (no tool calls)

Latest version

1.0.1, published 2026-10-28 (registry, as of the 2026-10-29 snapshot)

First listed version

2026-10-28 (earliest version still in the registry; older removed versions would be earlier)

Version history

2 versions listed, all on 2026-10-28; 2 in the 90 days before the 2026-10-29 snapshot.

Most recent 2 versions

1.0.1 · 2026-10-28
1.0.0 · 2026-10-28

(versions still listed in the registry only)

Registry data

snapshot 2026-10-29

Package and repository

checked 2026-10-29

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; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. 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

Version 1.0.0 (published 2026-10-28) → 1.0.1 (published 2026-10-28), between the registry lists of 2026-10-28 and 2026-10-29.

The publisher published no GitHub release note for this version: its repository publishes no GitHub releases.

Source: the official MCP Registry list on 2026-10-28 and on 2026-10-29; release notes from the GitHub Releases API, checked 2026-10-29.

What it is

What does this server offer?

Observed inventory

23tools

0resources

0prompts

None of its 23 tools are described as changing anything. For 23 the reading was uncertain, so no mark is shown.

akari_reddit_sentiment
“Reddit crypto sentiment analysis — crowd sentiment scan of crypto social feeds: top tickers ranked by bull/bear ratio with LONG/SHORT bias.”
Takes no inputs.
akari_confluence
“Hyperliquid perpetual funding rates crossed with Reddit sentiment — returns perps where funding and crowd bias agree, with the side that collects funding.”
Takes no inputs.
akari_meme_radar
“Meme coin radar — trending meme tokens with hype ratios from crypto social feeds.”
Takes no inputs.
akari_wallet_intel
“On-chain wallet intelligence for any EVM address on Base — live ETH and USDC balances via raw RPC; pass ?address=0x… .”
Takes no inputs.
akari_signal_execute
“Hyperliquid crypto trading signal — the funding+momentum confluence engine's current best setup as a complete signal: side, basis, entry parameters, leverage cap.”
Takes no inputs.
akari_feed
“Consolidated crypto trading signal feed — ONE schema-frozen JSON digest (akari.feed.v1) merging Hyperliquid funding+momentum long/short trading signals (v7.2 confluence gate), Reddit sentiment bias, …”
Takes no inputs.
akari_inplay_edge
“Polymarket in-play sports betting edge signals — live and armed football (soccer) matches across Premier League, La Liga, Serie A, Bundesliga, Ligue 1 and Champions League: our Poisson model probabil…”
Takes no inputs.
akari_batch
“Bulk wallet vetting — ONE call returns Base ETH + USDC balances for up to 50 EVM addresses (pass ?addresses=0xA,0xB,… or POST {"addresses":[…]}) at 50% of the single-call price.”
Takes no inputs.
akari_deep
“Deep wallet profile for x402 payer intelligence — pass ?address=0x… (GET) or {"address":"0x…"} (POST) and get ETH+USDC balances on Base, transaction count, contract detection, and the last ~50 minute…”
Takes no inputs.
akari_launch_kit
“Launch copy kit for token or agent projects — returns ready-to-post marketing copy generated deterministically from YOUR facts (no LLM, no invention): 3 taglines, a ≤280-char X post (with char count)…”
Takes no inputs.
akari_trade_plan
“Turnkey Hyperliquid trade tickets — executable order specs, not just a signal.”
Takes no inputs.
akari_hl_market
“Hyperliquid perpetuals market snapshot — every active coin (~180) with mark and oracle price, premium in bps, funding rate (8h + annualised APR) and which side collects it, open interest in USD, 24h …”
Takes no inputs.

Show 11 more tools

akari_ta
“TradingView technical-analysis snapshot for crypto — per-timeframe buy/sell/neutral ratings (1h, 4h, 1d, 1w), RSI, ATR and ATR%, 24h change, volume, 52-week range, plus a swing-weighted composite bia…”
Takes no inputs.
akari_desk_state
“Live trading desk state snapshot — Hyperliquid account equity and open perpetual positions (raw clearinghouse state), Polymarket cash and combined desk value from the latest desk mark, armed football…”
Takes no inputs.
akari_pass
“Desk Pass — one $5.00 payment buys 30 days of access to EVERY paid route on this server (feed, wallet-intel, TA, HL market, desk-state, confluence, meme-radar, trade-plan, launch-kit, in-play edge, a…”
Takes no inputs.
akari_endpoint_audit
“x402 endpoint audit — pass ?url=https://your.host and get the full per-route report for one paid endpoint: does every listed URL answer 402, does the payment-required header decode, is the amount pos…”
Takes no inputs.
akari_audit_plus
“x402 audit + fix plan — the full per-route probe, then a prioritised remediation plan keyed to every finding with the exact change to make (header, JSON field, file path), the estimated share of mach…”
Takes no inputs.
akari_market_report
“x402 market report — the measured state of the x402 seller market: how many of the sellers in the 402index directory actually serve a valid 402 challenge, how many listed endpoints are dead, the grad…”
Takes no inputs.
akari_catalog_report
“x402 catalog report — the only graded census of the CDP Bazaar discovery index: every host we probed (727 on 2026-10-28), how many answer a live 402, the A-F grade for each with its defect ids, and t…”
Takes no inputs.
akari_akash_deploy_kit
“Akash deployment kit — the exact SDL, boot-test and lease runbook we used to put a live container on Akash, including the four failure modes that cost us real attempts: deposits must be uact not uakt…”
Takes no inputs.
akari_picks
“Akari model picks — today's football picks where a last-6-form Poisson model beats the live Polymarket moneyline by 10+ points, with the model probability, the ask, the edge, and the settled hit-rate…”
Takes no inputs.
akari_alpha_brief
“Decision brief: market regime, ranked funding-carry edges that cleared the full gate set, the explicit avoid list, stand-down reasons and armed fixtures.”
2 inputs
- equitynumber
- risk_pctnumber
akari_board
“FREE: live edge board text summary (verdict, regime, passing edges, refusals).”
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. 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-29.

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: 0% of 2
Tools with a description: 100% of 23
Typical description length: 377 characters

The tool set

Counted from the listing

Tools: 23
Size of the list: about 3,698 tokens for an agent to load (characters ÷ 4)
Naming: 23 of 23 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 23 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-29 (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://akari-x402.puzzling-marten.workers.dev/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "akari-crypto-intel": {
      "url": "https://akari-x402.puzzling-marten.workers.dev/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "akari-crypto-intel": {
      "type": "http",
      "url": "https://akari-x402.puzzling-marten.workers.dev/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"akari-crypto-intel","type":"http","url":"https://akari-x402.puzzling-marten.workers.dev/mcp"}'

Claude Code

claude mcp add --transport http akari-crypto-intel https://akari-x402.puzzling-marten.workers.dev/mcp

Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)

{
  "mcpServers": {
    "akari-crypto-intel": {
      "type": "streamableHttp",
      "url": "https://akari-x402.puzzling-marten.workers.dev/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}

Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project

{
  "mcpServers": {
    "akari-crypto-intel": {
      "httpUrl": "https://akari-x402.puzzling-marten.workers.dev/mcp"
    }
  }
}

OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project

[mcp_servers.akari-crypto-intel]
url = "https://akari-x402.puzzling-marten.workers.dev/mcp"

Zed · Zed settings file (command: zed: open settings file)

{
  "context_servers": {
    "akari-crypto-intel": {
      "url": "https://akari-x402.puzzling-marten.workers.dev/mcp"
    }
  }
}

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://akari-x402.puzzling-marten.workers.dev/mcp --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 #6

The 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 akari-x402.puzzling-marten.workers.dev/mcp	Session opened	matches	our test · 2026-10-29
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-29
Repository github.com/edvyno/akari-x402-mcp	Opens publicly	matches	api.github.com · 2026-10-29

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.edvyno
GitHub owner: a personal account (edvyno)

Repository: github.com/edvyno/akari-x402-mcp
Stars: 0
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no

Source: the registry entry and api.github.com · 2026-10-29.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Tool list changes

Our reads compared · no tool called

Hosted endpoint akari-x402.puzzling-marten.workers.dev/mcp

1 of 1 comparison between consecutive reads showed a change (2 reads, 2026-10-28 to 2026-10-29; versions 1.0.0 to 1.0.1).

Last change seen between our reads on 2026-10-28 (version 1.0.0) and 2026-10-29 (version 1.0.1).

Added (4):

akari_akash_deploy_kitakari_audit_plusakari_catalog_reportakari_picks

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-10-29 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

4 of 4 record checks met · 4 do not apply · 1 not checked

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
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-29. 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. How each check works · Leaderboards

Common questions about io.github.edvyno/akari-crypto-intel

Answered from the data above

Who publishes io.github.edvyno/akari-crypto-intel?

The registry ties the namespace io.github.edvyno to the GitHub account edvyno; only its owner can publish under it. Its linked repository, github.com/edvyno/akari-x402-mcp, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.edvyno/akari-crypto-intel safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.edvyno/akari-crypto-intel need an API key or sign-in?

It opened a session without any credential on 2026-10-29. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.edvyno/akari-crypto-intel been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

Where is the source code of io.github.edvyno/akari-crypto-intel?

In github.com/edvyno/akari-x402-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A 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

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-29

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: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised

Not run, with the reason · 12

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
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or 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

Does not apply to this server · 4

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
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
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-29, 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,132 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 23 tools, 0 resources, 0 prompts.
4,991 msFinished: 2 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.

TopicAI-classified

pending: added in the weekly update

listed 2026-10-29; not classified yet

Pricing modelAI-classified

pending: added in the weekly update

the website is not read yet

Programming language

Python

api.github.com · 2026-10-29

Hosting type

remote (hosted by the publisher)

registry · 2026-10-29

MCP capability

tools

our test · 2026-10-29

Transport

streamable HTTP

registry · 2026-10-29

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-29

Lifecycle status

active

registry · 2026-10-29

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: a personal account · repository age: 0–30 days · stars: 0–9

api.github.com · 2026-10-29

Maintenance

active

api.github.com · 2026-10-29

Environment

the publisher's infrastructure

where it runs, from the hosting type

“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. “io.github.edvyno/akari-crypto-intel: MCP server record.” Data checked 2026-10-29. https://protocolprobe.com/mcp/servers/io.github.edvyno/akari-crypto-intel

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

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.edvyno/akari-crypto-intel)](https://protocolprobe.com/mcp/servers/io.github.edvyno/akari-crypto-intel)

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