RestDB (BYOK)
Read the collections, documents and media metadata of your restdb.io database with your own API key
Search public Figshare research data, papers and software, and read your own private items, collections and projects with your own personal token
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
get_accountlist_my_articlesget_my_articlelist_my_collectionslist_my_projectssearch_public_articlesSources: Live from the Figshare API (api.figshare.com) with a BYOK key; documentation: https://docs.figshare.com/. Endpoints checked against that documentation on 2026-10-16.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
11 tools, grouped by job. Every one is read-only or compute-only.
https://byok-figshare.connectorbay.com/mcpThree ways in, the same 11 tools.
https://byok-figshare.connectorbay.com/mcpPOST https://byok-figshare.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-figshare.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at figshare.com).Figshare (BYOK) lets an AI assistant read your own Figshare data through the Figshare API with a key you supply (Figshare personal token). It is a hosted MCP server with 11 tools such as Get account, List my articles, Get my article, List my collections, List my projects, Search public articles, published by Unify Dynamics LLC. It is independent and not affiliated with Figshare.
Add the MCP endpoint https://byok-figshare.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-figshare.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-figshare.json.
Yes: this is a bring-your-own-key connector. Create a Figshare personal token at https://figshare.com/account/applications and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
Read the collections, documents and media metadata of your restdb.io database with your own API key
Read your Retell AI account and platform setup: API key info, concurrency, integrations, CRM config, conversation flows, shared flow components and agent versions with your own API key
Read your Retell AI agent tests: test case definitions, batch test jobs, and test run results with pass, fail and error counts with your own API key
Read your Roadie software catalog entities, locations, and Tech Insights scorecards, checks and results with your own API token
Search the Roblox Creator Store for models, audio, decals and plugins, and read asset metadata, versions and upload operations with your own Open Cloud API key (read-only)
Read your Roboflow computer-vision workspace: projects, dataset versions, trained models and workflows, with your own API key
https://byok-figshare.connectorbay.com/mcpPOST https://byok-figshare.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-figshare.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-figshare.connectorbay.com/health · Tool schemas: https://byok-figshare.connectorbay.com/tools.jsonFigshare (BYOK) lets an AI assistant read your own Figshare data through the Figshare API with a key you supply (Figshare personal token). Read-only: 11 tools (get_account, list_my_articles, get_my_article, list_my_collections, list_my_projects, search_public_articles, list_public_articles, get_public_article, list_article_files, list_public_collections, get_public_collection). 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 api.figshare.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Figshare. Figshare 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:
get_account: Show the Figshare account the token belongs to: name, ORCID, storage quota and quota used.list_my_articles: List the items (articles, datasets, software) in your own Figshare account, including private drafts, with title, DOI and dates.get_my_article: Get one of your own items, including drafts: description, tags, categories, license, authors and files.list_my_collections: List the collections in your own Figshare account with title, DOI and publication date.list_my_projects: List the projects you can access in Figshare with your role and storage type.search_public_articles: Search public Figshare items (datasets, papers, posters, software) by text, with optional item type and date filters.list_public_articles: List public Figshare items, newest first by default, filtered by item type, institution, DOI or dates.get_public_article: Get one public Figshare item with description, authors, tags, categories, license, citation and file list.list_article_files: List the files of a public Figshare item with name, size, MIME type, checksum and download URL.list_public_collections: List public Figshare collections (curated groups of items) filtered by institution, DOI or dates.get_public_collection: Get one public Figshare collection with description, authors, tags, categories and the number of items.You bring your own Figshare Figshare personal token (https://figshare.com/account/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 api.figshare.com 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.
Live from the Figshare API (api.figshare.com) with a BYOK key; documentation: https://docs.figshare.com/. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Figshare. Figshare 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 Figshare account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Figshare (BYOK) is. Figshare (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Figshare data: Search public Figshare research data, papers and software, and read your own private items, collections and projects with your own personal token. You bring your own Figshare Figshare personal token; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Figshare 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 api.figshare.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Figshare 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 Figshare receives. The request we make on your behalf, including the key and the arguments, under Figshare's own terms and privacy policy. Figshare acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Figshare 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 Figshare 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. Figshare (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 Figshare at any time to end all access.
Children. Figshare (BYOK) is a general-audience service operated by the adult using the assistant, under Figshare's own age rules.
Changes. We will post changes here with a new effective date.
Effective 24 October 2026. These terms govern use of the Figshare (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-figshare.connectorbay.com/mcphttps://byok-figshare.connectorbay.com/openapi.jsonWhen 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. Figshare (BYOK) never asks for them.