Spydra
Spydra OpenRWA provides public-chain token store APIs for assets, tokens, sales, investments, investor workflows, payouts, and chain configuration.
Verdict
Common use cases
- Audit token allocations before investor calls
- Compare testnet and mainnet deployment status
- Pull investor holdings for compliance review
- Verify asset publication counts at month-end
- Check supported chains before new token launch
Integration
- Vendor
- Spydra
- Category
- other
- Auth
- API_KEY
- Tools
- 10
- Composio slug
spydra
Tools
- Get Asset
Return detailed information for one OpenRWA asset, optionally including token or token-sale projections.
- Get Asset Status Counts
Return asset counts grouped by publication status for the connected OpenRWA token store.
- List Assets
Return one numbered page of draft or published assets in the connected OpenRWA token store.
- List Asset Tokens
Return the tokens associated with one OpenRWA asset.
- List Chains
Return supported OpenRWA blockchain networks and their public network, currency, status, and fee attributes. test_mode=true is verified to return testnets; the provider currently does not reliably treat false as a mainnet-only filter.
- List Countries
Return the complete OpenRWA country reference list, including ISO codes, currencies, languages, and dialing codes.
- List Investors
Return one numbered page of investors registered with the connected OpenRWA token store.
- List Investor Tokens
Return one numbered page of tokens held or invested in by a specific OpenRWA investor.
- List Investor Transactions
Return one numbered page of mint, payout, burn, or token-creation transactions for a specific OpenRWA investor.
- List Token Sales
Search and filter one numbered page of OpenRWA token sales available through the connected store.
Setup
Setup guide
- 11. Open your Switchy workspace settings and navigate to the Integrations tab. 2. Search for Spydra and click Connect. 3. Paste your OpenRWA API key when prompted — retrieve it from your Spydra dashboard under API Credentials. 4. Grant read access to assets, tokens, investors, and chain metadata; the MCP does not request write scopes. 5. Save the connection and return to any Project. 6. Type '@Spydra list the first page of published assets' to confirm the integration works. 7. If you see asset records, the connection is live; if you get an authentication error, double-check the API key in workspace settings. 8. Use @Spydra in any message to invoke asset queries, token lookups, or investor reports — the MCP handles pagination and returns JSON you can parse inline.
What teammates see: by default, memories from Spydra are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Asset Inventory Snapshot
@Spydra list published assets and include token-sale projections for each one
Investor Token Holdings
@Spydra show me the tokens held by investor ID 12345
Chain Deployment Options
@Spydra list all supported chains including testnets and their fee attributes
Asset Status Breakdown
@Spydra get asset counts grouped by status for our token store
Country Reference Lookup
@Spydra return the complete country reference list with ISO codes and currencies
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@spydra list all published real-world assets in our token store and show me their current status counts
The connected OpenRWA store contains 12 published assets and 3 drafts. Published assets include: 4 real estate tokenizations (2 commercial properties in Dubai, 1 residential development in Austin, 1 mixed-use in Singapore), 5 commodity-backed tokens (gold, silver, carbon credits), and 3 revenue-share instruments. The real estate tokens represent $8.2M in aggregate underlying value. Two assets are currently in active token sales; the others have completed their initial offerings.
This example combines List Assets with Get Asset Status Counts to provide portfolio visibility. Requires API key with read access to the token store. The MCP returns paginated results—large portfolios may need multiple calls. Asset details reflect the store's configuration; test environments will show synthetic data.
@spydra fetch detailed information for asset ID RWA-2024-RE-001 including token sale projections and investor breakdown
Asset RWA-2024-RE-001 is a tokenized commercial office building in Dubai Marina. Property valuation: $4.5M. Token structure: 450,000 tokens at $10 each, minimum purchase 100 tokens. Current sale progress: 68% sold (306,000 tokens) across 47 investors. Projected completion: 14 days at current velocity. Token includes quarterly rental income distribution rights. Blockchain: Polygon mainnet. Compliance: KYC required, accredited investors only in US jurisdictions.
Get Asset with projection flags demonstrates the MCP's ability to surface both static metadata and dynamic sale metrics. The response shape depends on what the asset creator configured—not all RWA tokens include income rights or sale timelines. This read-only call does not modify asset state.
@spydra show me which blockchain networks support our token deployments and highlight any testnets we can use for staging
OpenRWA currently supports 8 production networks: Ethereum mainnet, Polygon, Binance Smart Chain, Avalanche C-Chain, Arbitrum, Optimism, Base, and Solana. All networks report 'active' status with standard gas fee structures. For staging, 5 testnets are available: Sepolia (Ethereum), Mumbai (Polygon), BSC Testnet, Fuji (Avalanche), and Arbitrum Sepolia. Testnets use native test currencies (SepoliaETH, MATIC, etc.). Note: testnet availability can change—verify chain status before deploying test tokens.
List Chains with test_mode filtering helps teams plan multi-chain deployments. The MCP surfaces network metadata but does not execute on-chain transactions—actual token deployment happens through separate Spydra APIs. Testnet reliability varies; the provider notes that test_mode behavior is not fully stable across all chains.
Use-case deep-dives
When tokenized-asset reporting beats spreadsheets for small funds
A 6-person real estate syndication team closes three tokenized property deals a year and needs monthly investor statements. Spydra's OpenRWA MCP is the right call if your assets are already on-chain and you're fielding repetitive Slack questions about token balances or sale projections. The Get Asset and List Investor Tokens tools let an AI pull live data without your CFO exporting CSVs. The threshold: if you're still structuring deals off-chain or your investors don't understand blockchain, this MCP won't simplify the workflow—it assumes tokenization is already your rails. For teams running 10+ tokenized assets with 50+ investors asking the same questions, Spydra turns repetitive lookups into one-prompt answers.
How Spydra speeds quarterly compliance checks for RWA issuers
A 3-person compliance team at a tokenized-bond issuer runs quarterly audits: matching on-chain token holders to KYC records, verifying no unauthorized transfers, and confirming asset metadata hasn't drifted. Spydra's MCP wins here because List Investors and List Asset Tokens surface the full holder registry in seconds, and Get Asset Status Counts flags unpublished drafts that shouldn't be live. The API-key auth keeps audit trails clean. The catch: if your token store spans multiple blockchains or you need historical snapshots beyond current state, the 10-tool scope gets limiting—you'll still export to a compliance platform for deep forensics. For quarterly spot-checks on a single-chain RWA program, this MCP cuts audit prep from two days to two hours.
When Spydra makes sense for NFT marketplace support teams
A 4-person support team at a tokenized art marketplace answers 30 tickets a day: 'Where's my token?', 'Why isn't my asset showing?', 'What chains do you support?' Spydra's MCP is a fit if your backend is OpenRWA and your agents waste time toggling between admin panels and blockchain explorers. List Chains and Get Asset let an AI answer chain questions and asset-lookup requests in one prompt. The limit: if your marketplace uses a custom contract standard or you need transaction-level debugging, Spydra's asset-centric tools won't drill deep enough—you'd want an Etherscan MCP instead. For teams handling high-volume, surface-level token inquiries on OpenRWA infrastructure, Spydra turns repetitive lookups into instant AI responses.
Frequently asked
What does the Spydra MCP do in Switchy?
It connects your Switchy workspace to Spydra's OpenRWA platform, letting AI agents query real-world asset tokenization data. You can retrieve asset details, investor holdings, token sale projections, and blockchain network configurations without writing API calls. Useful if your team manages tokenized assets or needs to pull RWA reference data into workflows.
Do I need admin access to connect Spydra?
You need a Spydra API key with read access to your OpenRWA token store. The MCP uses API_KEY authentication, so whoever connects it must have credentials that grant visibility into the assets, investors, and tokens you want to query. No OAuth flow—just paste the key into Switchy's integration settings.
Can the Spydra MCP create or update tokenized assets?
No. The ten tools are read-only: listing assets, fetching investor portfolios, checking publication status, and pulling blockchain network metadata. If you need to mint tokens or modify asset records, use Spydra's dashboard or write API directly. This MCP is for retrieval and reporting, not asset management.
How does this compare to querying Spydra's API directly?
The MCP wraps Spydra's REST endpoints so AI agents can call them in natural language. You skip writing fetch logic, parsing JSON, and handling pagination. Trade-off: you're limited to the ten exposed tools. If you need custom filtering or batch operations, the raw API gives you more control.
Who on the team should connect the Spydra integration?
Whoever holds the Spydra API key and understands which token store the team queries. Typically a finance or operations lead who manages RWA data. Once connected, any Switchy member can ask agents to pull asset or investor information without needing their own Spydra credentials.