Scientific Microservices
com.scientificmicroservicesPublished by scientificmicroservices.comOfficial publisherv1.0.0Updated Oct 24, 2026
Valid and reliable data engineering and statistical analysis without hallucinations.
Overview
A remote MCP endpoint that gives an assistant data engineering and statistical analysis capabilities, intended to produce valid, reliable results without halluc
- What you can do
- Scientific Microservices is a remote MCP server reached over streamable HTTP at a fixed provider endpoint. Its stated purpose is valid and reliable data engineering and statistical analysis without hallucinations. The manifest does not list individual tools, so the exact operations available are not documented here.
- When to use it
- Consider it when you want an assistant to carry out data engineering or statistical analysis tasks and prefer results grounded in a dedicated service rather than model guesswork. Because the tool list is not published, check the provider's documentation before relying on it for a specific workflow.
- Requirements
- A remote endpoint at the provider's host, reachable over streamable HTTP; no local package or runtime is needed. Authentication is OAuth and is required. Two headers must be supplied: email (required) and key (required, secret). The key is requested from the provider using the email address.
Installation
In SourceWeft
- Open Scientific Microservices in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.scientificmicroservices%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"scientific-microservices": {
"type": "http",
"url": "https://mcp.scientificmicroservices.com/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.