us.artificl/vendorping
REMOTE · VENDORPING.ARTIFICL.US · SCANNED SEP 24
Vendor document & expiry tracking for septic operators — read-only live demo board tools.
Available components
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 → Why this is hard to score →
Endpoint Security57
- 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 5 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 241 tokens (~48/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the us.artificl/vendorping MCP server?
us.artificl/vendorping is a hosted endpoint at https://vendorping.artificl.us/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · vendorping.artificl.us
claude mcp add --transport http us-artificl-vendorping 'https://vendorping.artificl.us/mcp'
{
"mcpServers": {
"us-artificl-vendorping": {
"url": "https://vendorping.artificl.us/mcp"
}
}
} {
"servers": {
"us-artificl-vendorping": {
"type": "http",
"url": "https://vendorping.artificl.us/mcp"
}
}
} [mcp_servers.us-artificl-vendorping] url = "https://vendorping.artificl.us/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"us-artificl-vendorping": {
"type": "remote",
"url": "https://vendorping.artificl.us/mcp",
"enabled": true
}
}
} openclaw mcp add us-artificl-vendorping --url 'https://vendorping.artificl.us/mcp' --transport streamable-http
mcp_servers:
us-artificl-vendorping:
url: "https://vendorping.artificl.us/mcp" {
"McpServers": {
"us-artificl-vendorping": {
"Transport": "http",
"Url": "https://vendorping.artificl.us/mcp"
}
}
} assistant mcp add us-artificl-vendorping -t streamable-http -u 'https://vendorping.artificl.us/mcp'
{
"mcpServers": {
"us-artificl-vendorping": {
"type": "http",
"url": "https://vendorping.artificl.us/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- 8 Sept 26 0
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
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 24 Sept 2026 · Probed https://vendorping.artificl.us/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vendorping.artificl.us | CN=WR3,O=Google Trust Services,C=US | 3 Aug 2026 | 1 Nov 2026 | RSA 2048 | SHA256-RSA | c4b37957de8d752609cbf80e01cac8e3 |
| SANs: vendorping.artificl.us | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of vendorping.artificl.us. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| us. | present | 59017 | 8 | Verified |
| artificl.us. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vendorping.artificl.us/mcp | Verified | 200 | |
| http (plaintext) | http://vendorping.artificl.us/mcp | HTTPS enforced | 302 | https://vendorping.artificl.us/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
export_vendor_report ~32
Export the full vendor document report as CSV text (vendor, doc type, due date, status, request history).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_compliance_summary ~35
Get the compliance dashboard summary: totals for tracked, missing, expired/overdue, due this week, and awaiting review.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_expiring_docs ~57
List vendor documents expiring within the next N days (default 30), including ones already received, so renewals can be requested before they lapse.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Look-ahead window in days (default 30). |
No output schema declared.
No examples provided.
list_missing_docs ~39
List every vendor document that is still missing (not yet received), most critical first — expired/overdue at the top, then by days remaining.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_vendor_docs ~78
Search tracked vendor documents by vendor name or document type. Returns matching records with status (validated, received, missing, overdue) and expiry dates.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Text to match against vendor name or document type (case-insensitive; industry shorthand like "COI" or "med card" works). Omit to list everything. |
No output schema declared.
No examples provided.
What is the us.artificl/vendorping MCP server?
us.artificl/vendorping is an MCP server listed in the public MCP registry as us.artificl/vendorping. Vendor document & expiry tracking for septic operators, read-only live demo board tools. This page covers its hosted endpoint (https://vendorping.artificl.us/mcp).
Is the us.artificl/vendorping MCP server safe to use?
us.artificl/vendorping scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the us.artificl/vendorping MCP server expose?
us.artificl/vendorping exposes 5 tools: search_vendor_docs, list_missing_docs, get_expiring_docs, get_compliance_summary, export_vendor_report. Their descriptions and schemas cost roughly 241 tokens of context every time the server is loaded.
Does the us.artificl/vendorping MCP server require authentication?
No. We connected to us.artificl/vendorping without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the us.artificl/vendorping MCP server still maintained?
us.artificl/vendorping is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.