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

RIVET / AliEV EV Charging Site Intelligence

REMOTE · ALIEV.BASE44.APP

Start with analyze_ev_site(address) for a free, source-backed EV charging opportunity screen.

Available components

−9 this week 76 Trust /100

Last scanned (21 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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

Endpoint Security83
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 418 tokens (~69/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 17 Nov 26 −11
    • Stability: pass → 0.20 functional
  • 11 Nov 26 +59
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 18 Oct 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.77 → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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

Captured 21 Nov 2026 · Probed https://aliev.base44.app/functions/alievMcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.base44.app CN=YR2,O=Let's Encrypt,C=US 11 Nov 2026 9 Feb 2027 RSA 2048 SHA256-RSA 60242839d924e3cf2c79a57e3ebe91d4b46
SANs: *.base44.app, base44.app
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of aliev.base44.app. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
base44.app. DS published 2371 13 Verified
aliev.base44.app. Verified address RRset verified with the apex keys
Authentication No authorisation required

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

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
content-security-policy script-src 'none'; object-src 'none';
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://aliev.base44.app/functions/alievMcp Verified 200
http (plaintext) http://aliev.base44.app/functions/alievMcp HTTPS enforced 301 https://aliev.base44.app/functions/alievMcp
MCP tools · 6 exposed · ~418 tokens

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

Tool Tokens
analyze_ev_site ~94

PRIMARY TOOL for property-specific EV questions. If the user gives a street address and asks whether EV charging makes sense, what charging competition is nearby, or whether the property has EV opportunity, call this tool FIRST without calling the offer catalog first. Returns a free source-backed screen, explicit unknowns, and the exact next paid-handoff path. Does not perform engineering, utility approval or payment.

NameTypeReqDescription
addressstringyes–

No output schema declared.

No examples provided.

get_aliev_capabilities ~41

Describe AliEV machine-facing capabilities and boundaries. For a property-specific EV question with an address, prefer analyze_ev_site instead of stopping at capability discovery.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_aliev_offers ~61

Use AFTER a site screen or when the human explicitly asks for pricing or paid AliEV options. Do not use this as the first tool for a property-specific EV question when an address is available. Read-only and never creates a checkout or payment obligation.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_aliev_purchase_status ~65

Check an AliEV purchase and, when both purchase key and checkout session are supplied, allow AliEV to re-verify provider payment before reporting paid state. Read-only from the buyer perspective.

NameTypeReqDescription
purchase_keystring––
session_idstring––

No output schema declared.

No examples provided.

prepare_paid_handoff ~65

Create a human review link for a selected AliEV paid-depth option. This tool does not create a checkout, invoice, payment obligation, entitlement, or outreach.

NameTypeReqDescription
addressstring––
offer_keystringyes–
request_idstring––

No output schema declared.

No examples provided.

prepare_site_report_checkout ~92

After the human explicitly agrees to pay, prepare secure checkout for the $299 Preliminary Site Report or $750 Full Site Report. Requires buyer email and site address. Checkout creation is not payment proof or report fulfillment.

NameTypeReqDescription
addressstringyes–
emailstringyes–
offer_keystringyes–
request_idstring––
user_confirmed_paymentbooleanyes–

No output schema declared.

No examples provided.

Install

How do I install the RIVET / AliEV EV Charging Site Intelligence MCP server?

RIVET / AliEV EV Charging Site Intelligence is a hosted endpoint at https://aliev.base44.app/functions/alievMcp, 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 · aliev.base44.app

# add to Claude Code
claude mcp add --transport http jgaethle10-aliev 'https://aliev.base44.app/functions/alievMcp'
Common questions

What is the RIVET / AliEV EV Charging Site Intelligence MCP server?

RIVET / AliEV EV Charging Site Intelligence is an MCP server listed in the public MCP registry as io.github.jgaethle10/aliev. Start with analyze_ev_site(address) for a free, source-backed EV charging opportunity screen. This page covers its hosted endpoint (https://aliev.base44.app/functions/alievMcp).

Is the RIVET / AliEV EV Charging Site Intelligence MCP server safe to use?

RIVET / AliEV EV Charging Site Intelligence scores 76 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 RIVET / AliEV EV Charging Site Intelligence MCP server expose?

RIVET / AliEV EV Charging Site Intelligence exposes 6 tools: analyze_ev_site, get_aliev_offers, prepare_paid_handoff, prepare_site_report_checkout, get_aliev_purchase_status, get_aliev_capabilities. Their descriptions and schemas cost roughly 418 tokens of context every time the server is loaded.

Does the RIVET / AliEV EV Charging Site Intelligence MCP server require authentication?

No. We connected to RIVET / AliEV EV Charging Site Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the RIVET / AliEV EV Charging Site Intelligence MCP server still maintained?

RIVET / AliEV EV Charging Site Intelligence is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the RIVET / AliEV EV Charging Site Intelligence MCP server?

VerifyMCP ran 13 checks on RIVET / AliEV EV Charging Site Intelligence, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.