MCP servers › io.usefulapi › rinkel
MCP server · registry snapshot 2026-10-24 · last tested 2026-10-24
io.usefulapi/rinkel
Read Rinkel calls, voicemails, contacts and numbers; add call notes, edit contacts, block numbers. — the publisher's description
Summary
io.usefulapi/rinkel is a remote MCP server listed in the official MCP registry at version 1.0.0. On 2026-10-24 ProtocolProbe connected to it in read-only mode and read its inventory: 27 tools, 0 resources and 1 prompt.
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
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Sign-in
- none needed to open a session
- Repository
- public
- Tools
- 27
- Last tested
- 2026-10-24
Observed fact
This server accepted a session without any credential and lists 7 tools whose name or declaration suggests they change data (rinkel_add_call_note, rinkel_update_call_note, rinkel_delete_call_note, rinkel_create_contact, rinkel_update_contact and 2 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-24.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-24
- Mode
- read-only (no tool calls)
- Latest version
- 1.0.0, published 2026-10-24 (registry, as of the 2026-10-24 snapshot)
- First listed version
- 2026-10-24 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-10-24
- Package and repository
- checked 2026-10-24
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Changes since the last refresh
New in the registry: not in the list of 2026-10-23, listed on 2026-10-24 with version 1.0.0 (published 2026-10-24).
Source: the official MCP Registry list on 2026-10-23 and on 2026-10-24.
What it is
What does this server offer?
Observed inventoryNone of its 27 tools are described as changing anything. For 27 the reading was uncertain, so no mark is shown.
- rinkel_list_calls
“List call detail records (inbound and outbound calls) with date, direction, status (ANSWERED, MISSED, VOICEMAIL, ANSWERING_SERVICE), duration, external and internal number, the users involved, notes,…”
Publisher declares: read-only yes
24 inputs
filterstring“Free-text search over calls.”internal_numbersarray“Only calls on these internal (Rinkel) numbers, as listed by rinkel_list_numbers.”external_numberstring“Only calls with this external (caller or callee) number.”date_presetstring“A relative period.”start_datestring“Only calls on or after this date (yyyy-mm-dd, or an ISO date-time with timezone).”end_datestring“Only calls on or before this date (yyyy-mm-dd = end of that day UTC, or an ISO date-time with timezone).”has_notesboolean“Only calls that have (true) or lack (false) notes.”is_anonymousboolean“Only calls from a hidden number (true) or not (false).”contact_lookupboolean“Include the matching contact in each record.”pageinteger“Page number (default 1).”per_pageinteger“Items per page (default 10, max 50).”directionsarray“Only these directions.”statusesarray“Only these call outcomes.”user_idsarray“Only calls handled by these user ids (rinkel_list_users).”sentimentsarray“Only calls with this AI-insights sentiment.”duration_presetarray“Duration buckets in minutes ('30-0' = 30 minutes or more).”min_duration_secondsinteger“Minimum duration in seconds (ignored with duration_preset).”max_duration_secondsinteger“Maximum duration in seconds (ignored with duration_preset).”has_transcriptionboolean“Only calls that have a transcription.”has_insightsboolean“Only calls that have AI insights.”include_detailsboolean“Include insights and notes in each record.”contactstring“Only calls with this contact (id).”sortstring“Sort field (default date).”sort_orderstring“Sort order (default DESC).”
- rinkel_get_call
“Get one call detail record by its Rinkel id (the `id` field of rinkel_list_calls): numbers, users, status, duration, notes, voicemail and call-recording ids, AI insights.”
Publisher declares: read-only yes
1 input, 1 required
call_record_idstringrequired“The call detail record id (`id`).”
- rinkel_get_call_by_network_id
“Get one call detail record by its network `callId` (the id Rinkel sends in webhook events), optionally with insights and notes.”
Publisher declares: read-only yes
2 inputs, 1 required
network_call_idstringrequired“The network call id (`callId` field).”include_detailsboolean“Include insights and notes.”
- rinkel_get_call_transcription
“Get the raw transcription of a call by its network `callId` (needs Rinkel AI insights on the account; 404 when the call has none).”
Publisher declares: read-only yes
1 input, 1 required
network_call_idstringrequired“The network call id (`callId` field of the call record).”
- rinkel_get_call_recording_url
“Get a temporary URL (valid 3 hours) to stream or download a call recording.”
Publisher declares: read-only yes
1 input, 1 required
call_recording_idstringrequired“The call recording id (`callRecording.id` of a call record).”
- rinkel_list_voicemails
“List voicemail messages (call records with status VOICEMAIL): caller, date, duration, whether new, and the voicemail id.”
Publisher declares: read-only yes
14 inputs
filterstring“Free-text search over calls.”internal_numbersarray“Only calls on these internal (Rinkel) numbers, as listed by rinkel_list_numbers.”external_numberstring“Only calls with this external (caller or callee) number.”date_presetstring“A relative period (overrides start_date and end_date).”start_datestring“Only calls on or after this date (yyyy-mm-dd, or an ISO date-time with timezone).”end_datestring“Only calls on or before this date (yyyy-mm-dd = end of that day UTC, or an ISO date-time with timezone).”has_notesboolean“Only calls that have (true) or lack (false) notes.”is_anonymousboolean“Only calls from a hidden number (true) or not (false).”contact_lookupboolean“Include the matching contact in each record.”pageinteger“Page number (default 1).”per_pageinteger“Items per page (default 10, max 50).”is_newboolean“Only unplayed voicemails (true).”topicsarray“Only voicemails with these AI topic ids.”sort_orderstring“Sort order by date (default DESC).”
- rinkel_count_new_voicemails
“Number of voicemails that have not been played yet.”
Publisher declares: read-only yes
Takes no inputs.
- rinkel_get_voicemail_url
“Get a temporary URL (valid 3 hours) to stream or download a voicemail.”
Publisher declares: read-only yes
1 input, 1 required
voicemail_idstringrequired“The voicemail id (`voicemail.id`).”
- rinkel_list_contacts
“List the contacts shared with everyone in the account (plus the Rinkel system contact, tag 'system'): names, company, phone numbers, email.”
Publisher declares: read-only yes
4 inputs
filterstring“Search by name, company or number.”letterstring“Only contacts whose name starts with this letter.”pageinteger“Page number (default 1).”per_pageinteger“Items per page (default 10, max 50).”
- rinkel_get_contact
“Get one contact by id.”
Publisher declares: read-only yes
1 input, 1 required
contact_idstringrequired“The contact id.”
- rinkel_find_contact_by_number
“Find the contact that owns a phone number (E.164 such as +31612345678 works best).”
Publisher declares: read-only yes
1 input, 1 required
phone_numberstringrequired“The phone number, preferably in E.164 format (+31612345678).”
- rinkel_list_users
“List the account's users: name, email, phone number, role (ADMIN, USER, ANSWERINGSERVICE), availability schedule and status, and `fixed`/device info (`deviceId` is needed to start a call).”
Publisher declares: read-only yes
1 input
include_avatarsboolean“Include avatar URLs.”
Show 15 more tools
- rinkel_get_user
“Get one user by id, including preferences, notification settings, schedule and `deviceId`.”
Publisher declares: read-only yes
2 inputs, 1 required
user_idstringrequired“The user id (rinkel_list_users).”include_avatarboolean“Include avatar URLs.”
- rinkel_list_numbers
“List the account's Rinkel phone numbers: id, label, number, status (ACTIVE, SUSPENDED, PENDING_PORTING_IN ...), activation date and the users assigned.”
Publisher declares: read-only yes
Takes no inputs.
- rinkel_get_number
“Get one Rinkel number with its full dial plan: greeting, business hours schedule, call forwarding targets and ring logic, voice menu, call recording and caller-id settings.”
Publisher declares: read-only yes
1 input, 1 required
number_idstringrequired“The number id (rinkel_list_numbers).”
- rinkel_list_recordings
“List the uploaded audio recordings used in the dial plan (greetings, announcements, voice-over scripts): name, description, duration and where each is used.”
Publisher declares: read-only yes
4 inputs
pageinteger“Page number (default 1).”per_pageinteger“Items per page (default 10, max 999).”sortstring“Sort field (default date).”sort_orderstring“Sort order (default DESC).”
- rinkel_list_webhooks
“List the webhook subscriptions (events incomingCall, outgoingCall, callStart, callEnd, callInsights) with URL and active flag.”
Publisher declares: read-only yes
Takes no inputs.
- rinkel_validate_phone_number
“Check a phone number for a country and return its normalised form.”
Publisher declares: read-only yes
3 inputs, 2 required
country_iso_codestringrequired“Country code such as NL or BE.”numberstringrequired“The number without the country calling code.”check_inventoryboolean“Also check availability to order.”
- rinkel_add_call_note
“WRITE: add a note to a call record (visible to everyone in the account who sees the call).”
Publisher declares: read-only no · destructive no · idempotent no
2 inputs, 2 required
call_record_idstringrequired“The call record id (`id` of rinkel_list_calls).”contentstringrequired“The note text.”
- rinkel_update_call_note
“WRITE: replace the text of an existing note on a call record (the note id is in `notes[].id` of the call record).”
Publisher declares: read-only no · destructive yes · idempotent yes
3 inputs, 3 required
call_record_idstringrequired“The call record id (`id`).”note_idstringrequired“The note id (`notes[].id`).”contentstringrequired“The new note text.”
- rinkel_delete_call_note
“WRITE, irreversible: delete one note from a call record.”
Publisher declares: read-only no · destructive yes · idempotent yes
3 inputs, 2 required
call_record_idstringrequired“The call record id (`id`).”note_idstringrequired“The note id (`notes[].id`).”confirmboolean“Must be true, set only after the user explicitly approved this exact action.”
- rinkel_create_contact
“WRITE: create a contact.”
Publisher declares: read-only no · destructive no · idempotent no
6 inputs, 1 required
first_namestringlast_namestringcompany_namestringemailstringnumbersarrayrequired“Phone numbers of the contact (Rinkel requires at least one).”default_outbound_number_idstring“Id of the Rinkel number to call this contact from (rinkel_list_numbers).”
- rinkel_update_contact
“WRITE: update a contact (PUT semantics).”
Publisher declares: read-only no · destructive yes · idempotent yes
7 inputs, 2 required
contact_idstringrequired“The contact id.”first_namestringlast_namestringcompany_namestringemailstringnumbersarrayrequired“The COMPLETE list of numbers (replaces the stored ones; Rinkel requires at least one, so read the contact first and resend the ones to keep).”default_outbound_number_idstring“Resend the current value to keep it; omit to clear it.”
- rinkel_delete_contact
“WRITE, irreversible: delete a contact for the whole account.”
Publisher declares: read-only no · destructive yes · idempotent yes
2 inputs, 1 required
contact_idstringrequired“The contact id.”confirmboolean“Must be true, set only after the user explicitly approved this exact action.”
- rinkel_block_number
“WRITE: block a number from calling ANY of the account's numbers.”
Publisher declares: read-only no · destructive no · idempotent yes
2 inputs, 1 required
numberstringrequired“E.164 number (+31612345678), 'anonymous', or a prefix wildcard like '+3161*'.”reasonstring“Why it is blocked (for example Spam).”
- rinkel_unblock_number
“WRITE: remove a number (or the same wildcard pattern that was blocked) from the block list so it can call again.”
Publisher declares: read-only no · destructive no · idempotent yes
1 input, 1 required
numberstringrequired“The blocked entry exactly as it was blocked.”
- rinkel_start_call
“WRITE, COSTS CALL MINUTES: starts a real phone call.”
Publisher declares: read-only no · destructive yes · idempotent no
5 inputs, 3 required
device_idstringrequired“The id of the user device that starts the call (`deviceId` of a user).”tostringrequired“The number to call, in E.164 format (+31612345678).”number_idstringrequired“The id of the Rinkel number used as caller id (rinkel_list_numbers).”anonymousboolean“Hide the caller id (default false).”confirmboolean“Must be true, set only after the user explicitly approved this exact action.”
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-24.
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
- 91% of 92
- Tools with a description
- 100% of 27
- Typical description length
- 211 characters
The tool set
Counted from the listing
- Tools
- 27
- Size of the list
- about 6,161 tokens for an agent to load (characters ÷ 4)
- Naming
- 27 of 27 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 27 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-24 (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://rinkel.usefulapi.io/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"rinkel": {
"url": "https://rinkel.usefulapi.io/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"rinkel": {
"type": "http",
"url": "https://rinkel.usefulapi.io/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"rinkel","type":"http","url":"https://rinkel.usefulapi.io/mcp"}'Claude Code
claude mcp add --transport http rinkel https://rinkel.usefulapi.io/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://rinkel.usefulapi.io/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- 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). 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 verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint rinkel.usefulapi.io/mcp | Session opened | matches | our test · 2026-10-24 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-10-24 |
| Repository github.com/m190/usefulapi-mcp | Opens publicly | matches | api.github.com · 2026-10-24 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.usefulapi · 409 servers
- GitHub owner
- a personal account (m190)
- Repository
- github.com/m190/usefulapi-mcp
- Stars
- 0
- Repository age
- 91–180 days
- Last push
- 0–30 days ago
- Archived
- no
Source: the registry entry and api.github.com · 2026-10-24.
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.
Choosing
Record checks
Public records · not a safety rating4 of 4 record checks met · 4 do not apply · 1 not checked
- 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-24. 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.usefulapi/rinkel
Answered from the data aboveIs io.usefulapi/rinkel 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.usefulapi/rinkel need an API key or sign-in?
It opened a session without any credential on 2026-10-24. The registry entry declares no required credential; no declaration is not a guarantee.
Has io.usefulapi/rinkel been security tested?
Partly. 3 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. No security verdict is published before verification.
Where is the source code of io.usefulapi/rinkel?
In github.com/m190/usefulapi-mcp, which opens publicly.
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: not run · nothing to check it against
- Fake assistant turns: not run · an error was returned
- 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
3 exercised13 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). 3 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 - 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 - 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 - 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server returned an error when its prompts were read.not run · an error was returned - 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-24, 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
- 327 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 27 tools, 0 resources, 1 prompt.
- 1,478 msFinished: 3 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. “io.usefulapi/rinkel: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/io.usefulapi/rinkel
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/io.usefulapi/rinkel)
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