OrganisationIndependent
SYNTAAI
GitHub@SYNTAAIlast push
Provides
Agent access to your systemsABAPAgent access to your systemsGiving an AI agent access to the business data, configuration or operations of systems you run through an MCP server. [Serving your application over MCP](capability:mcp-servers) exposes your own service contract; system access reaches the systems behind it, and one implementation may do both. Development assistance belongs to [agent access to your code](capability:agent-code-access).
Entries
Group by
EntrySignals
Maintains
sap-security-mcpsap-security-mcpAn entirely read-only security analysis surface: nineteen tools, five resources and eight prompts for audits, SOX and segregation-of-duties review, behind OAuth 2.0 with PKCE. The vendor hosts an endpoint, and the README documents running it yourself.independent, abap
Read-only does not mean low-stakes: a complete picture of who can do what in an SAP system is exactly what an attacker would want, and the ready-made endpoint is the vendor's rather than yours — the README also documents running the server yourself. The authentication is careful; the question of what leaves your landscape is still yours.
Read-only security analysis MCP server for SAP audits and SoD review
Details
History
- sap-security-mcpThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.
- sap-security-mcpCorrected against the README, whose Deployment section documents running server.py yourself with OAuth.
- sap-security-mcpTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README. Filed on the BTP door because there is no door for the SAP product it fronts and hard rule 9 allows one — the same strain recorded on the LeanIX entries.
- First entry seenDiscovered via sap-ai-mcp-servers.
For your agent
- Ref
actor:syntaai- JSON
- /actors/syntaai.json
- MCP
- Connecting an agent