PJM vs MISO Energy Arbitrage Oracle
REMOTE · ENERGY-ARBITRAGE.IO · SCANNED SEP 20
PJM/MISO energy arbitrage. Intel TDX attested, on-chain every 60 min. MCP tools for AI agents.
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 yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the PJM vs MISO Energy Arbitrage Oracle MCP server?
PJM vs MISO Energy Arbitrage Oracle is a hosted endpoint at https://energy-arbitrage.io/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 · energy-arbitrage.io
claude mcp add --transport http dornansgar390-hue-energy-oracle 'https://energy-arbitrage.io/mcp'
{
"mcpServers": {
"dornansgar390-hue-energy-oracle": {
"url": "https://energy-arbitrage.io/mcp"
}
}
} {
"servers": {
"dornansgar390-hue-energy-oracle": {
"type": "http",
"url": "https://energy-arbitrage.io/mcp"
}
}
} [mcp_servers.dornansgar390-hue-energy-oracle] url = "https://energy-arbitrage.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dornansgar390-hue-energy-oracle": {
"type": "remote",
"url": "https://energy-arbitrage.io/mcp",
"enabled": true
}
}
} openclaw mcp add dornansgar390-hue-energy-oracle --url 'https://energy-arbitrage.io/mcp' --transport streamable-http
mcp_servers:
dornansgar390-hue-energy-oracle:
url: "https://energy-arbitrage.io/mcp" {
"McpServers": {
"dornansgar390-hue-energy-oracle": {
"Transport": "http",
"Url": "https://energy-arbitrage.io/mcp"
}
}
} assistant mcp add dornansgar390-hue-energy-oracle -t streamable-http -u 'https://energy-arbitrage.io/mcp'
{
"mcpServers": {
"dornansgar390-hue-energy-oracle": {
"type": "http",
"url": "https://energy-arbitrage.io/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.
- 20 Sept 26 0
- Transport: pass → fail ▼ security
- TLS certificate: unverified → pass ▲ security
- 19 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: fail → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 18 Sept 26 +20
- HSTS header: unverified → fail ▼ security
- TLS certificate: pass → unverified ▼ security
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- 17 Sept 26 0
- HSTS header: fail → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- 14 Sept 26 0
- HSTS header: unverified → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- 13 Sept 26 0
- HSTS header: fail → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- 12 Sept 26 0
- Transport: Transport check failed: the endpoint responded but didn't complete an MCP handshake over streamable-http. security
- 11 Sept 26 23
First indexed and scored.
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 20 Sept 2026 · Probed https://energy-arbitrage.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=energy-arbitrage.io | CN=YE2,O=Let's Encrypt,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5226f7f750587f2b63a0d924dea9228996d |
| SANs: energy-arbitrage.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of energy-arbitrage.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| energy-arbitrage.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://energy-arbitrage.io/mcp | Unreachable | ||
| http (plaintext) | http://energy-arbitrage.io/mcp | HTTPS enforced | 308 | https://energy-arbitrage.io/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 →
build_subscription_tx Build Subscription Transaction ~152
Generate the cryptographic transaction calldata required to purchase a subscription on Arbitrum One. Output covers a two-step payload: ERC-20 RLC token approve followed by contract purchaseSubscription. This tool strictly builds calldata and does not submit transactions; the calling agent must sign and broadcast the payload externally.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_address | string | yes | EVM address of the agent that will receive the subscription, e.g. 0x1234... |
| sponsor_address | – | – | Optional EVM address of a sponsor who pays for the agent's subscription |
| tier | integer | yes | Subscription tier: 0 = 1 day ($20), 1 = 3 days ($50), 2 = 7 days ($100) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
check_subscription Check Subscription ~52
Check whether an EVM address has an active subscription. Returns expiry timestamp and human-readable info.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The agent's EVM address (0x...), e.g. 0x1234... |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_connection_info Connection Info ~41
Retrieve integration and transport configuration guides for connecting this oracle to AI clients (Claude Desktop, Cursor, MCP clients), including the complete list of accessible tools and capabilities.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_oracle_info Oracle General Info ~59
Retrieve comprehensive metadata for the PJM vs MISO Energy Arbitrage Oracle: smart contract address, Arbitrum One network, Intel TDX attestation status, and available subscription pricing tiers. Use as the primary initialization step for any agent workflow.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_oracle_status Oracle Status ~52
Check the real-time operational status of the oracle contract. Returns whether the system is ACTIVE or in MAINTENANCE, along with total active subscribers. Use this tool to verify system availability before requesting premium telemetry.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_sdk_template Get SDK Template ~54
Get the FULL Python SDK code (ai_agent_oracle_client.py). Auto-cycle: check subscription → purchase (approve + purchase, RLC) → read signal. Suitable for non-MCP agents running on web3.py.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_subscription_cost Get Subscription Cost ~67
Current subscription cost in RLC (dynamic, pegged to USD). Returns live cost from on-chain contract.
| Name | Type | Req | Description |
|---|---|---|---|
| tier | integer | yes | Subscription tier: 0 = 1 day ($20), 1 = 3 days ($50), 2 = 7 days ($100) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_telemetry Get Telemetry ~107
Retrieve the premium analytical energy signal computed inside the Intel TDX enclave. Returns the complete spatial arbitrage vector (direction: -1, 0, +1) and current price spread index between PJM and MISO. Executed as a static on-chain view call. Requires an active, unexpired paid RLC subscription for the provided address.
| Name | Type | Req | Description |
|---|---|---|---|
| subscriber_address | string | yes | EVM address that has an active RLC subscription, e.g. 0x1234... |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
is_arbitrage_profitable Is Arbitrage Profitable ~59
Evaluate the instantaneous financial viability of spatial electricity arbitrage between PJM West Hub and MISO Indiana Hub wholesale markets. Returns a boolean profitability indicator. Use as a zero-friction pre-flight check before deciding to purchase a full telemetry subscription.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the PJM vs MISO Energy Arbitrage Oracle MCP server?
PJM vs MISO Energy Arbitrage Oracle is an MCP server listed in the public MCP registry as io.github.dornansgar390-hue/energy-oracle. PJM/MISO energy arbitrage. Intel TDX attested, on-chain every 60 min. MCP tools for AI agents. This page covers its hosted endpoint (https://energy-arbitrage.io/mcp).
Is the PJM vs MISO Energy Arbitrage Oracle MCP server safe to use?
PJM vs MISO Energy Arbitrage Oracle scores 43 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 PJM vs MISO Energy Arbitrage Oracle MCP server expose?
PJM vs MISO Energy Arbitrage Oracle exposes 9 tools: get_oracle_info, get_oracle_status, check_subscription, get_subscription_cost, is_arbitrage_profitable, and 4 more. Their descriptions and schemas cost roughly 643 tokens of context every time the server is loaded.
Does the PJM vs MISO Energy Arbitrage Oracle MCP server require authentication?
Its publisher declares no required credentials for PJM vs MISO Energy Arbitrage Oracle. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the PJM vs MISO Energy Arbitrage Oracle MCP server still maintained?
PJM vs MISO Energy Arbitrage Oracle is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 18 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.