FishBase MCP. Query common names and species documentation.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
FishBase provides access to the world's largest database of fish species and marine organisms. Use this MCP server to query common names, track database versions, and access technical documentation for both FishBase and SeaLifeBase.
Your AI client can list species common names, check API status, and retrieve schema details for complex biological data analysis.
What your AI agents can do
Get docs
Gets general metadata and documentation for the FishBase API.
Get docs by table
Retrieves the specific documentation and schema details for a single database table.
Get heartbeat
Checks the current status and connectivity of the FishBase API.
The agent lists common names for a given fish species, supporting pagination and filtering to handle large sets of results.
The agent runs get_heartbeat to confirm the FishBase API is online and functioning correctly.
The agent retrieves a list of available FishBase/SeaLifeBase database versions, allowing historical data tracking.
The agent queries get_docs_by_table to pull the schema and metadata for any designated database table.
The agent calls get_docs to retrieve general metadata and documentation about the FishBase API structure.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
FishBase MCP Server: 5 Tools for Marine Data
These tools let your agent access everything from common name lists to deep schema documentation across the FishBase and SeaLifeBase databases.
019e5d19get docs
Gets general metadata and documentation for the FishBase API.
019e5d19get docs by table
Retrieves the specific documentation and schema details for a single database table.
019e5d19get heartbeat
Checks the current status and connectivity of the FishBase API.
019e5d19get versions
Lists all available database versions for FishBase and SeaLifeBase.
019e5d19list comnames
Accesses and filters common names data for fish species, supporting pagination.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with FishBase, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
FishBase gives your AI client access to the world's largest database of fish and marine organisms. You can query common names, track database versions, and check technical documentation for both FishBase and SeaLifeBase directly. Your agent lists common names for fish species using list_comnames, supporting filtering and pagination to handle huge result sets.
It checks the API status and connectivity with get_heartbeat to confirm the FishBase API is online and running right. You retrieve a list of available FishBase/SeaLifeBase database versions using get_versions, which lets you track historical data. You pull the schema and metadata for any specific database table by calling get_docs_by_table.
You get general metadata and documentation about the entire FishBase API structure by calling get_docs.
How FishBase MCP Works
- 1 First, your AI client calls a specific tool (e.g.,
list_comnames) and passes required parameters like the species ID or search criteria. - 2 The MCP Server executes the tool, contacting the FishBase/SeaLifeBase API, and retrieves the requested data (e.g., a list of common names, or a schema definition).
- 3 The data returns to your AI client, which then presents the information to you in a readable format.
The bottom line is that your agent handles the API calls and data formatting, so you just tell it what biological data you need.
Who Is FishBase MCP For?
Marine biologists, ichthyologists, and data scientists who need reliable, structured species data. If you're tired of cross-referencing multiple academic databases or manually checking API documentation, this server gives your agent a single, powerful source for fish species information.
Verifies species data and common names across different geographic regions without leaving the agent interface.
Accesses comprehensive taxonomic information and metadata for large-scale research projects.
Understands the FishBase schema and available data versions (get_versions) to structure complex, multi-source datasets.
What Changes When You Connect
- Need to verify a species' common name across regions? Use
list_comnames. It handles filtering and pagination, so you don't hit data limits when querying rare species. - Don't waste time checking if the API is up. Run
get_heartbeatfirst. You get instant confirmation that the FishBase API is live, keeping your workflow moving. - Working with historical data?
get_versionsshows you every database iteration, letting you pinpoint data from a specific year or release. - Confused by the schema? Use
get_docs_by_table. It pulls the exact metadata for any table, so you know precisely what data you're pulling. - You can check both FishBase and SeaLifeBase in one go. The server lets your agent switch between the two major marine organism databases.
- The whole system is designed for structured data. Getting this data means you can feed it directly into Python scripts or analysis tools without cleanup.
Real-World Use Cases
Mapping regional names for a new species catalog.
A marine biologist needs to list common names for Gadus morhua across Europe and North America. Instead of searching three different regional databases, the agent runs list_comnames. It returns a comprehensive list, which the biologist can then use to build the catalog.
Researching data changes over time.
A data scientist is comparing species records from 2010 vs. 2020. They use get_versions to identify the exact database versions available, then use get_docs_by_table to ensure the schema remained consistent between those years.
Debugging a complex data pipeline.
A research student is getting weird data results. They first use get_heartbeat to confirm the API is online. Then, they use get_docs to review the general API documentation, quickly spotting a change in the required input format.
Building a cross-database comparison tool.
A developer needs to build a tool comparing data from both FishBase and SeaLifeBase. They use the server's dual database support feature to run queries against both sources in a single agent session.
The Tradeoffs
Treating the API like a single endpoint
Trying to get documentation, check the status, and list names all in one massive, poorly structured prompt. The agent gets confused, runs nothing, and you waste time.
→
Use specific tools. First, run get_heartbeat. Then, run list_comnames with your parameters. Finally, if you need schema details, call get_docs_by_table. Keep the calls separate and targeted.
Forgetting to check data availability
Running a massive data query using list_comnames without checking if the necessary database versions are available, leading to a failure mid-run.
→
Before querying, run get_versions. This confirms the data source supports the time range you need. Then, proceed with your data pull using list_comnames.
Assuming all data is in one place
Running a query against FishBase data when the required information actually resides only in SeaLifeBase, causing the agent to return incomplete results.
→ Be explicit. Tell your agent to use both databases. The server supports querying both FishBase and SeaLifeBase within the same workflow.
When It Fits, When It Doesn't
Use this if your task requires verifying biological data, checking schemas, or listing common names for fish species. You need a reliable, single source for ichthyological records. Don't use this if you just need to send a message or manage user accounts—you'll use a messaging tool for that. If you need to process large-scale, non-biological data, look for a different data source. This server is specialized for FishBase and SeaLifeBase data.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by FishBase. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 5 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Manually checking species data across academic sites is a huge time sink.
Today, verifying a species name often means opening several tabs: the regional database, the taxonomic guide, and the API documentation. You spend time switching between sites, copying IDs, and cross-referencing schema differences just to confirm a common name. It's tedious, and you'll inevitably miss a data point.
With FishBase, your agent handles the whole process. You ask for the common names, and the system runs `list_comnames`. You get the structured, peer-reviewed data you need, without ever leaving your chat window.
FishBase MCP Server: Get structured species records.
You no longer need to manually check the API health or look up the schema in a separate document. You simply ask your agent to check the status using `get_heartbeat` or ask for the table documentation using `get_docs_by_table` right alongside your main query.
The difference is that the data is immediately actionable. It's not just a dump of text; it's structured data ready for analysis or direct publication.
Common Questions About FishBase MCP
How do I check if the FishBase API is online using `get_heartbeat`? +
You run get_heartbeat directly. The server checks the current status and time, confirming the API is up and running. If it returns a successful signal, you know you can proceed with data queries.
Can I list common names for fish species with `list_comnames`? +
Yes, list_comnames accesses common names data for fishes. You can specify filters and pagination parameters to ensure you retrieve all the required results.
How do I find the schema for a specific table in SeaLifeBase? +
Use get_docs_by_table and specify the table name and whether you are querying SeaLifeBase. This tool returns the exact metadata and documentation for that specific table.
Does FishBase support multiple databases? +
Yes. The server is built to support both FishBase and SeaLifeBase, allowing your agent to switch between the two major marine organism sources easily.
What is `get_versions` for in the FishBase MCP Server? +
get_versions lists available database versions. This is crucial for scientific research that requires tracking how data or schemas changed over time.
How do I find documentation for a table in the FishBase API using `get_docs_by_table`? +
You use get_docs_by_table to get the schema documentation for a specific table. This tells you exactly what data columns are available in that database table.
Does `list_comnames` support filtering or pagination? +
Yes, list_comnames supports both filtering and pagination. You can narrow down your search results or handle large datasets by specifying parameters.
How do I check which database versions are available using `get_versions`? +
get_versions lists all available database versions. You can select a specific version to ensure your analysis uses historical or required data snapshots.
Can I switch between FishBase and SeaLifeBase data? +
Yes. Most tools include a use_sealifebase parameter. Set it to true to query the SeaLifeBase database instead of the default FishBase.
How do I find the common names for a specific fish species? +
Use the list_comnames tool and provide the species name in the species parameter. You can also limit the results or filter specific fields.
Where can I find documentation for the database tables? +
You can use get_docs for general metadata or get_docs_by_table to get detailed documentation for a specific table name.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
CockroachDB Cloud
Manage distributed SQL clusters via CockroachDB Cloud — track clusters, monitor nodes, and audit network allowlists directly from any AI agent.
Chroma (Vector DB)
Manage vector embeddings via Chroma — list collections, query embeddings, and audit document counts directly from any AI agent.
MongoDB Atlas Vector Search
Manage vector storage via MongoDB Atlas — perform similarity searches, query MQL documents, and audit collections.
You might also like
Fusion Operations
Optimize factory floor operations with real-time production tracking, worker scheduling, and quality control automation.
Mobile Action
All-in-one app marketing intelligence via Mobile Action — track ASO, keywords, and ad creatives directly from your AI agent.
Bugcrowd
Manage crowdsourced security via Bugcrowd — track submissions, programs, and targets directly from any AI agent.