axisdirect-rapidapi-mcp

Created By
abhaybrajaa year ago
This MCP (Model Context Protocol) server wraps the AxisDirect API via RapidAPI, exposing Get Profile, Get Order Book, Order History, etc.,
Overview

what is axisdirect-rapidapi-mcp?

axisdirect-rapidapi-mcp is a Model Context Protocol (MCP) server that wraps the AxisDirect API via RapidAPI, providing access to various financial data endpoints such as Get Profile, Get Order Book, and Order History.

how to use axisdirect-rapidapi-mcp?

To use this MCP server, you need to integrate it with your application via RapidAPI. You can make API calls to retrieve financial data by using the provided endpoints.

key features of axisdirect-rapidapi-mcp?

  • Access to financial profiles and order books
  • Historical order data retrieval
  • Easy integration through RapidAPI

use cases of axisdirect-rapidapi-mcp?

  1. Fetching user profiles for financial analysis
  2. Retrieving order books for trading applications
  3. Accessing historical order data for reporting and analytics

FAQ from axisdirect-rapidapi-mcp?

  • What endpoints are available?

The MCP server exposes endpoints like Get Profile, Get Order Book, and Order History.

  • Is there a cost to use the API?

The API is available through RapidAPI, and pricing may vary based on usage.

  • What programming language is used?

The server is built using Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
abhaybraja
Star
1
Language
Python
License
MIT license
Category
finance
Tags

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

21 hours ago