
Entry Risk Score
io.github.entryriskscorev1.0.0Updated Oct 7, 2026
Entry-risk score for Binance USDT-M perpetuals: how risky is entering now. Not a signal.
Overview
AI-generated overview
A remote MCP server that returns an entry-risk score for Binance USDT-M perpetual futures, indicating how risky entering a position is right now.
- What it does
- It provides an entry-risk score for Binance USDT-M perpetual contracts, answering how risky it is to enter a position at the current moment. The description states it is not a trading signal. No individual tools are listed in the manifest, so the exact tool surface is not documented here.
- When to use it
- Worth adding when an assistant needs a quick risk read on timing an entry into Binance USDT-M perpetuals, for example to add context to a trading discussion. It is not a signal generator, so it should not be used as standalone trade advice.
- Requirements
- A remote MCP endpoint at entryriskscore.com over streamable HTTP. It requires an API key sent in the X-API-Key header; keys start with ers_ and can be created in the provider's dashboard under API & MCP, with 7-day trial keys available. Network access to the endpoint is needed.
Before you install
The X-API-Key header carries a secret credential and must be kept private. The service is explicitly described as not a signal, so its output should not be treated as trading advice. The endpoint is third-party and remote, so requests and any data sent to it leave the user's machine.
Installation
In SourceWeft
- Open Entry Risk Score in the dashboard and add it to a workspace.
- 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.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"entry-risk-score": {
"type": "http",
"url": "https://entryriskscore.com/api/v1/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestOct 7, 2026

