List MCP resources
curl --request GET \
--url https://statusstack.com/api/v1/mcp/resources \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://statusstack.com/api/v1/mcp/resources', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://statusstack.com/api/v1/mcp/resources"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"data": {}
}{
"jsonrpc": "2.0",
"error": {
"code": 123,
"message": "<string>",
"data": {}
},
"id": "<string>"
}{
"jsonrpc": "2.0",
"error": {
"code": 123,
"message": "<string>",
"data": {}
},
"id": "<string>"
}{
"jsonrpc": "2.0",
"error": {
"code": 123,
"message": "<string>",
"data": {}
},
"id": "<string>"
}MCP
List MCP resources
REST convenience for the JSON-RPC resources/list method.
GET
/
v1
/
mcp
/
resources
List MCP resources
curl --request GET \
--url https://statusstack.com/api/v1/mcp/resources \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://statusstack.com/api/v1/mcp/resources', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://statusstack.com/api/v1/mcp/resources"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text){
"data": {}
}{
"jsonrpc": "2.0",
"error": {
"code": 123,
"message": "<string>",
"data": {}
},
"id": "<string>"
}{
"jsonrpc": "2.0",
"error": {
"code": 123,
"message": "<string>",
"data": {}
},
"id": "<string>"
}{
"jsonrpc": "2.0",
"error": {
"code": 123,
"message": "<string>",
"data": {}
},
"id": "<string>"
}Authorizations
mcpAuthmcpApiKey
MCP credentials, distinct from v1 API keys. Either an MCP connection key (mcp_sk_...,
created from the customer dashboard) or an OAuth 2.1 access token carrying the mcp:use
scope. Credentials are never accepted in the query string. A refused request answers
401 with a WWW-Authenticate header naming the protected resource metadata, so
OAuth-capable clients can discover the authorization server.
Query Parameters
Response
The resources/list result
The result of the equivalent JSON-RPC call.
Was this page helpful?

