orisha-data

com.orisha-dataPublished by orisha-data.comv0.1.1Updated Oct 24, 2026

MCP server for x402 paid market-data endpoints.

VerifiedSTDIODesktop onlyFinance Business & Commerce

Server details

Identifier: com.orisha-data/orisha-data-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to orisha-data.com. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.orisha-data%2Forisha-data-mcp.svg)](https://sourceweft.com/mcp/com.orisha-data%2Forisha-data-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that connects an assistant to x402 paid market-data endpoints, with optional EVM private-key signing for paid calls.

What you can do: Connect an assistant to x402 paid market-data endpoints through a configurable base URL and network setting. Preview tools can be used without a key, while paid x402 tools require an EVM private key supplied through the environment. The manifest lists no individual tools, so the exact data endpoints and query capabilities are not documented here.
When to use it: Consider it when an assistant needs market data from x402-priced endpoints and you are prepared to pay per call with an EVM wallet. It is less suitable if you only need free data or cannot manage a signing key.
Requirements: Runs locally over stdio, launched with npx from the npm package orisha-data-mcp, so Node.js is needed. Configure the ORISHA_DATA_BASE_URL and ORISHA_X402_NETWORK environment variables; paid tools also need ORISHA_MCP_EVM_PRIVATE_KEY. Network access to the data endpoints is required. Desktop only.

Before you install

Paid x402 tools spend money per call and require an EVM private key in ORISHA_MCP_EVM_PRIVATE_KEY, so use a dedicated low-balance wallet and keep the key out of shared logs. Requests go to third-party endpoints set by ORISHA_DATA_BASE_URL. The manifest lists no tools, so verify what each call does and costs before enabling paid use.

Installation

In SourceWeft

Open orisha-data in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.1LatestSep 16, 2026

Score

15% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.