IOC Exchange (BYOK)

IOC Exchange (BYOK) — connector documentation

• MCP endpoint: https://byok-ioc-exchange.connectorbay.com/mcp
• REST API: POST https://byok-ioc-exchange.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-ioc-exchange.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own IOC Exchange access token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-ioc-exchange.connectorbay.com/health · Tool schemas: https://byok-ioc-exchange.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-ioc-exchange · agent@connectorbay.com

What IOC Exchange (BYOK) is for

IOC Exchange (BYOK) lets an AI assistant read your own IOC Exchange data through the IOC Exchange API with a key you supply (access token). Read-only: 12 tools (verify_credentials, get_account, lookup_account, list_account_posts, public_timeline, hashtag_timeline, home_timeline, trending_tags, trending_posts, search_accounts, search_posts, list_notifications). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to ioc.exchange. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by IOC Exchange. IOC Exchange and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which ioc.exchange account is my token connected to?"
• "How many followers does ioc.exchange account 1 have?"
• "What is the account ID of Gargron on ioc.exchange?"
• "What has ioc.exchange account 1 posted recently?"
• "What is being posted publicly on ioc.exchange right now?"
• "Show recent posts tagged #opensource on ioc.exchange"

What it does

• verify_credentials: Show the ioc.exchange account the token belongs to: handle, display name, bio, follower and post counts.
• get_account: Get one account's public profile by its ID: handle, bio, bot flag, follower, following and post counts, last post date.
• lookup_account: Find an account by handle (for example 'Gargron' for a local user) and return its ID and profile counts.
• list_account_posts: List an account's posts, newest first, with text (HTML), date, counts and tags. Can skip replies and boosts.
• public_timeline: List recent public posts on ioc.exchange (local and federated), newest first, optionally only local, remote or with media.
• hashtag_timeline: List recent public posts that use one hashtag, newest first.
• home_timeline: List the latest posts from the accounts you follow, newest first (needs the read:statuses scope).
• trending_tags: List hashtags that were used more than usual over the past week, with daily use and account counts.
• trending_posts: List posts that are getting more interaction than others right now, with counts and author.
• search_accounts: Search accounts on ioc.exchange by name or handle and return matching profiles.
• search_posts: Full-text search of posts on ioc.exchange (needs a token; results depend on the server's search setup).
• list_notifications: List your notifications (mentions, boosts, favourites, follows) newest first (needs the read:notifications scope).

BYOK key

You bring your own IOC Exchange access token (https://ioc.exchange/settings/applications). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to ioc.exchange over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://docs.joinmastodon.org/methods/ (the API this connector calls, with a BYOK key)

Live from the IOC Exchange API (ioc.exchange) with a BYOK key; documentation: https://docs.joinmastodon.org/methods/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by IOC Exchange. IOC Exchange and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your IOC Exchange account.

Built for: Worldwide. Languages: English.

IOC Exchange (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What IOC Exchange (BYOK) is. IOC Exchange (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own IOC Exchange data: Read timelines, profiles, hashtags, trends, notifications and search on ioc.exchange (general-interest server) with your own access token. You bring your own IOC Exchange access token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one IOC Exchange call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to ioc.exchange, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If IOC Exchange rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What IOC Exchange receives. The request we make on your behalf, including the key and the arguments, under IOC Exchange's own terms and privacy policy. IOC Exchange acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer IOC Exchange gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your IOC Exchange data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. IOC Exchange (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at IOC Exchange at any time to end all access.

Children. IOC Exchange (BYOK) is a general-audience service operated by the adult using the assistant, under IOC Exchange's own age rules.

Changes. We will post changes here with a new effective date.

IOC Exchange (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the IOC Exchange (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. IOC Exchange (BYOK) provides: Read timelines, profiles, hashtags, trends, notifications and search on ioc.exchange (general-interest server) with your own access token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own IOC Exchange credentials and only access data you are allowed to access. IOC Exchange's terms apply to your use of IOC Exchange; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by IOC Exchange. IOC Exchange and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data IOC Exchange returns, lightly trimmed; it may be incomplete, delayed or changed by IOC Exchange. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your IOC Exchange account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent IOC Exchange's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; IOC Exchange may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your IOC Exchange key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action IOC Exchange takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-ioc-exchange

IOC Exchange (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-ioc-exchange.connectorbay.com/mcp
• REST API: https://byok-ioc-exchange.connectorbay.com/openapi.json
• Live status: https://byok-ioc-exchange.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. IOC Exchange (BYOK) never asks for them.