Server Details
The Manifold Markets MCP server provides comprehensive access to prediction market features, enabling users to create and manage markets, execute trades, and manage liquidity through a clean interface. It facilitates sophisticated market interactions with Manifold's platform, including market discovery, trading operations, information retrieval for users and portfolios, and social features like following markets and transferring mana.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
5 toolsget-betsTry in Inspector
Get bets from markets or for users with various filtering options
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Optional. Bet ID to filter by | |
| after | No | Optional. Get bets after this bet ID | |
| kinds | No | Optional. Filter by bet kind | |
| limit | No | Optional. Number of bets to return (default: 1000) | |
| order | No | Optional. Sort order by creation time | |
| before | No | Optional. Get bets before this bet ID | |
| userId | No | Optional. User ID to filter by | |
| answerId | No | Optional. Answer ID to filter by | |
| username | No | Optional. Username to filter by | |
| afterTime | No | Optional. Get bets after this timestamp | |
| minAmount | No | Optional. Minimum bet amount | |
| beforeTime | No | Optional. Get bets before this timestamp | |
| contractId | No | Optional. Contract ID(s) to filter by | |
| contractSlug | No | Optional. Contract slug to filter by | |
| filterRedemptions | No | Optional. Filter redemptions |
get-marketTry in Inspector
Get detailed information about a specific market
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Market ID |
get-userTry in Inspector
Get user information by username
| Name | Required | Description | Default |
|---|---|---|---|
| username | Yes | Username |
search-marketsTry in Inspector
Search for prediction markets with optional filters
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Sort order (default: score) | |
| term | Yes | Search query | |
| limit | No | Max number of results (default: 100) | |
| filter | No | Filter by question state. Resolved means the event has happened. (default: all) | |
| offset | No | Offset for pagination (default: 0) | |
| creatorId | No | Optional. Creator (user) ID to filter by | |
| contractType | No | Question type (default: ALL) |
search-usersTry in Inspector
Search for users by username or display name
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number for pagination (default: 0) | |
| term | Yes | Search query for username or display name | |
| limit | No | Max number of results (default: 500) |
To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!