{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-sap-abap-mcp-server-sdk","slug":"sap-abap-mcp-server-sdk","name":"SAP ABAP MCP Server SDK","type":"mcp","url":"https://github.com/abap-ai/mcp","page_url":"https://unfragile.ai/sap-abap-mcp-server-sdk","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-sap-abap-mcp-server-sdk__cap_0","uri":"capability://tool.use.integration.mcp.server.instantiation.from.abap.configuration.tables","name":"mcp server instantiation from abap configuration tables","description":"Dynamically creates MCP server instances at runtime using the ZCL_MCP_SERVER_FACTORY class, which reads server metadata from ABAP configuration tables (ZMCP_*) and instantiates the appropriate server class via reflection. The factory pattern decouples server configuration from deployment, enabling zero-code-change server registration and multi-tenant server hosting within a single ABAP system.","intents":["Register a new MCP server without recompiling the framework code","Host multiple independent MCP servers in one SAP system","Dynamically enable/disable servers via configuration table changes"],"best_for":["SAP system administrators managing multiple AI integration endpoints","Enterprise teams deploying MCP servers across R/3 and S/4HANA landscapes"],"limitations":["Configuration table changes require manual activation; no hot-reload without system restart","Server class must exist in ABAP system before factory can instantiate it","No built-in versioning or rollback mechanism for configuration changes"],"requires":["SAP ABAP 7.52+ (or 7.02 with downport compatibility)","Access to ZMCP_* configuration tables with INSERT/UPDATE/DELETE permissions","Custom server class implementing ZCL_MCP_SERVER_BASE interface"],"input_types":["configuration table entries (server name, class name, authentication method)"],"output_types":["instantiated server object implementing MCP protocol"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-sap-abap-mcp-server-sdk__cap_1","uri":"capability://tool.use.integration.json.rpc.2.0.protocol.parsing.and.method.routing","name":"json-rpc 2.0 protocol parsing and method routing","description":"The ZCL_MCP_JSONRPC class parses incoming HTTP request bodies as JSON-RPC 2.0 messages, validates structure (jsonrpc version, method, params, id), and routes method calls to the appropriate handler on the instantiated server. Implements full JSON-RPC 2.0 spec including error response formatting, batch request handling, and notification support (fire-and-forget calls with no id field).","intents":["Parse and validate MCP client requests in JSON-RPC 2.0 format","Route MCP method calls (initialize, resources/list, tools/call, etc.) to server handlers","Generate properly formatted JSON-RPC error responses for invalid requests"],"best_for":["ABAP developers building MCP servers that must comply with JSON-RPC 2.0 spec","Teams integrating SAP systems with MCP-compliant AI clients (Claude Desktop, LLM frameworks)"],"limitations":["No support for batch request optimization; processes requests sequentially","Error responses follow JSON-RPC 2.0 spec but may not include ABAP-specific context in error messages","Notification handling (requests without id) discards responses; no logging of notification outcomes by default"],"requires":["HTTP request body containing valid JSON-RPC 2.0 message","Server instance with methods matching MCP protocol (initialize, resources/list, tools/call, etc.)","ABAP JSON parsing library (native to 7.52+)"],"input_types":["JSON-RPC 2.0 request object (method, params, id, jsonrpc)"],"output_types":["JSON-RPC 2.0 response object or error response"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-sap-abap-mcp-server-sdk__cap_10","uri":"capability://tool.use.integration.http.request.routing.to.mcp.servers.based.on.icf.path.configuration","name":"http request routing to mcp servers based on icf path configuration","description":"Routes incoming HTTP requests to appropriate MCP servers based on ICF service path configuration. The ZCL_MCP_HTTP_HANDLER parses the request path, looks up the corresponding server in configuration tables, instantiates the server via the factory, and dispatches the request. Supports multiple servers per ICF service with path-based routing (e.g., /mcp/server1, /mcp/server2).","intents":["Host multiple MCP servers under a single ICF service endpoint","Route requests to the correct server based on URL path","Configure server routing without code changes"],"best_for":["SAP administrators managing multiple MCP servers in a single system","Teams consolidating MCP endpoints to reduce ICF service management overhead"],"limitations":["Path-based routing is simple string matching; no regex or pattern-based routing","Server lookup requires configuration table access on every request; adds latency (~5-10ms)","No built-in caching of server configuration; configuration changes require manual refresh","No support for dynamic path parameters beyond simple path segments"],"requires":["ICF service configured with HTTP handler pointing to ZCL_MCP_HTTP_HANDLER","Configuration table entries mapping paths to server classes"],"input_types":["HTTP request with path (e.g., /mcp/server1)"],"output_types":["routed request to appropriate server instance"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-sap-abap-mcp-server-sdk__cap_11","uri":"capability://data.processing.analysis.abap.native.json.processing.and.utility.functions.for.mcp.protocol.handling","name":"abap-native json processing and utility functions for mcp protocol handling","description":"Provides utility classes for JSON serialization/deserialization, schema validation, and data type conversion within ABAP. Leverages ABAP's native JSON support (CALL TRANSFORMATION, /ui2/cl_json) to handle MCP protocol messages and custom data structures. Includes helpers for converting ABAP types to JSON-serializable formats and vice versa.","intents":["Serialize ABAP data structures to JSON for MCP protocol responses","Deserialize JSON from MCP client requests into ABAP types","Convert between ABAP and JSON data types (dates, decimals, nested structures)"],"best_for":["ABAP developers implementing custom MCP servers with complex data structures","Teams handling data type conversions between ABAP and JSON-based MCP protocol"],"limitations":["ABAP JSON serialization may not preserve all type information (e.g., decimal precision)","Circular references in ABAP structures cause serialization errors; requires custom handling","Date/time formats must be explicitly converted to ISO 8601 for JSON compatibility","Large nested structures may exceed JSON serialization limits or cause performance issues"],"requires":["ABAP 7.52+ with native JSON support","Properly structured ABAP types (classes or structures) for serialization"],"input_types":["ABAP data structure or JSON string"],"output_types":["JSON string or ABAP data structure"],"categories":["data-processing-analysis","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-sap-abap-mcp-server-sdk__cap_12","uri":"capability://code.generation.editing.development.and.testing.utilities.for.mcp.server.validation","name":"development and testing utilities for mcp server validation","description":"Provides development tools and demo server examples (zcl_mcp_demo_server_stateless) for testing MCP server implementations. Includes utilities for validating MCP protocol compliance, testing tool invocation, and debugging request/response flows. Demo servers demonstrate best practices for resource, tool, and prompt implementation.","intents":["Test MCP server implementations before deployment","Validate protocol compliance with MCP specification","Learn MCP server development patterns from demo examples"],"best_for":["ABAP developers new to MCP server development","Teams validating custom server implementations against MCP spec"],"limitations":["Demo servers are stateless examples; may not cover all stateful patterns","Testing utilities are basic; no built-in integration with SAP testing frameworks (ABAP Unit)","No automated protocol compliance testing; validation is manual or requires custom test code","Demo servers use simplified business logic; real-world implementations require custom validation"],"requires":["ABAP development environment with access to demo server source code","HTTP client for testing MCP endpoints (e.g., Postman, curl)"],"input_types":["MCP protocol requests (JSON-RPC format)"],"output_types":["MCP protocol responses with validation feedback"],"categories":["code-generation-editing","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-sap-abap-mcp-server-sdk__cap_13","uri":"capability://automation.workflow.session.cleanup.and.lifecycle.management.for.long.running.mcp.servers","name":"session cleanup and lifecycle management for long-running mcp servers","description":"Provides utilities (zmcp_clear_mcp_sessions program) for managing session lifecycle, including automatic cleanup of expired sessions and manual session termination. Prevents memory leaks from accumulated session state in long-running ABAP systems. Supports configurable session timeout and cleanup policies.","intents":["Automatically clean up expired MCP sessions to prevent memory leaks","Manually terminate sessions for debugging or security purposes","Monitor session lifecycle and resource usage"],"best_for":["SAP system administrators managing long-running MCP servers","Teams deploying MCP servers in production with high session volume"],"limitations":["Cleanup is batch-based; no real-time session eviction","No built-in monitoring or alerting for session resource usage","Manual cleanup program must be scheduled via SAP job scheduler; no automatic background cleanup","Session timeout is global; no per-session or per-user configurable TTL"],"requires":["Access to zmcp_clear_mcp_sessions program","SAP job scheduler (SM36) for scheduling automated cleanup"],"input_types":["session cleanup parameters (timeout threshold, session IDs to delete)"],"output_types":["cleanup report (sessions deleted, memory freed)"],"categories":["automation-workflow","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-sap-abap-mcp-server-sdk__cap_14","uri":"capability://tool.use.integration.mcp.specification.version.support.and.protocol.evolution.handling","name":"mcp specification version support and protocol evolution handling","description":"Supports multiple MCP specification versions (2025-03-28 and 2025-06-18) with version negotiation during the initialize handshake. Handles protocol evolution by validating client-requested capabilities against server-supported features, enabling forward/backward compatibility as the MCP spec evolves. Version information is exchanged during initialization to ensure client/server compatibility.","intents":["Support multiple MCP specification versions in a single server","Negotiate protocol version with MCP clients during initialization","Handle protocol evolution without breaking existing clients"],"best_for":["Teams deploying MCP servers that must support multiple client versions","Enterprises managing long-lived MCP servers across protocol version upgrades"],"limitations":["Version negotiation is static; no feature-level negotiation (e.g., optional capabilities)","Backward compatibility requires maintaining code for older protocol versions; increases maintenance burden","No automatic migration of client requests between protocol versions; clients must upgrade","Version mismatch errors may not provide clear guidance on required upgrades"],"requires":["Server implementation supporting multiple MCP specification versions","Client capability to send version information during initialize"],"input_types":["client-requested MCP specification version"],"output_types":["server-supported MCP specification version and capabilities"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-sap-abap-mcp-server-sdk__cap_2","uri":"capability://safety.moderation.http.request.authentication.and.authorization.via.abap.security.model","name":"http request authentication and authorization via abap security model","description":"The ZCL_MCP_HTTP_HANDLER class validates incoming HTTP requests using ABAP's native authentication (user credentials, SSO tokens) and authorization (transaction codes, authorization objects). Integrates with SAP's ICF framework to extract user context and enforces ABAP-level access control before routing to MCP servers, enabling fine-grained permission control per server or per tool.","intents":["Authenticate MCP clients using SAP user credentials or SSO tokens","Enforce ABAP authorization objects to restrict which users can access specific MCP servers","Audit MCP server access by integrating with SAP's security audit log"],"best_for":["Enterprise SAP deployments requiring compliance with existing user/role management","Teams integrating MCP servers into secured SAP landscapes with role-based access control"],"limitations":["Authentication relies on SAP's ICF framework; external OAuth/JWT tokens require custom adapter code","Authorization checks are ABAP-level only; no built-in fine-grained tool-level permissions (e.g., restrict specific tool calls per user)","No support for API key or token-based authentication out-of-the-box; requires custom extension"],"requires":["SAP user account with appropriate authorization objects assigned","ICF service configured with authentication enabled","ABAP authorization objects defined for MCP server access (custom per deployment)"],"input_types":["HTTP request headers (Authorization, Cookie, or SSO token)"],"output_types":["authenticated user context (username, roles, authorization objects)"],"categories":["safety-moderation","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-sap-abap-mcp-server-sdk__cap_3","uri":"capability://safety.moderation.cors.policy.management.for.cross.origin.mcp.client.requests","name":"cors policy management for cross-origin mcp client requests","description":"The ZCL_MCP_HTTP_HANDLER manages CORS headers (Access-Control-Allow-Origin, Access-Control-Allow-Methods, Access-Control-Allow-Headers) for HTTP requests from MCP clients, with policies configurable via ABAP configuration tables. Handles preflight OPTIONS requests and enforces origin whitelisting to prevent unauthorized cross-origin access to MCP servers.","intents":["Allow MCP clients running in web browsers (Claude Desktop, web-based AI tools) to call ABAP MCP servers","Restrict MCP server access to whitelisted origins for security","Configure CORS policies per server without code changes"],"best_for":["Teams deploying MCP servers accessible from web-based AI clients or browser extensions","Enterprise deployments requiring strict origin control for MCP endpoints"],"limitations":["CORS is a browser-level security mechanism; does not protect non-browser clients (e.g., CLI tools, server-to-server calls)","Wildcard origin (*) disables CORS protection; configuration table must enforce specific origins","No support for credential-based CORS (Access-Control-Allow-Credentials); all requests treated as non-credentialed"],"requires":["Configuration table entries defining allowed origins per server","HTTP client capable of sending Origin header (typically web browsers or fetch API)"],"input_types":["HTTP Origin header from client request"],"output_types":["CORS response headers (Access-Control-Allow-Origin, etc.)"],"categories":["safety-moderation","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-sap-abap-mcp-server-sdk__cap_4","uri":"capability://memory.knowledge.stateful.and.stateless.session.management.for.mcp.interactions","name":"stateful and stateless session management for mcp interactions","description":"Supports multiple session management strategies (stateful with server-side session storage, stateless with client-provided context) via configurable session handlers. Stateful mode stores session state in ABAP memory or database tables, enabling multi-request conversations; stateless mode validates client-provided tokens/context without server-side storage, reducing memory overhead. Session lifecycle is managed per MCP client connection with configurable timeout and cleanup.","intents":["Maintain conversation state across multiple MCP client requests (stateful mode)","Scale MCP servers horizontally without session affinity (stateless mode)","Automatically clean up expired sessions to prevent memory leaks"],"best_for":["Teams building multi-turn MCP interactions requiring conversation context","High-scale deployments needing stateless session handling for load balancing"],"limitations":["Stateful sessions require server-side storage (ABAP memory or database); adds latency and memory overhead","Stateless mode requires client to send session token with each request; no automatic session persistence","Session timeout is global; no per-session configurable TTL","No built-in session replication across ABAP instances; requires external session store for multi-instance deployments"],"requires":["Session handler class implementing session interface","For stateful mode: ABAP memory or database table for session storage","For stateless mode: cryptographic key for session token signing/validation"],"input_types":["session identifier (cookie, header, or client-provided token)"],"output_types":["session context object with user/request state"],"categories":["memory-knowledge","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-sap-abap-mcp-server-sdk__cap_5","uri":"capability://data.processing.analysis.json.schema.based.input.output.validation.for.mcp.tools.and.resources","name":"json schema-based input/output validation for mcp tools and resources","description":"Implements JSON Schema validation for tool parameters and resource outputs using ABAP's native JSON schema support. Schemas are defined in configuration or code and validated at runtime before tool execution and after resource retrieval, ensuring type safety and preventing malformed data from reaching business logic or being returned to MCP clients. Generates validation errors in JSON-RPC format when schemas are violated.","intents":["Validate tool input parameters against defined JSON schemas before execution","Ensure resource outputs conform to declared schemas before returning to MCP clients","Generate clear validation error messages for schema violations"],"best_for":["Teams building MCP tools with strict input validation requirements","Enterprise deployments requiring data quality guarantees for AI-generated tool calls"],"limitations":["Schema validation adds latency (~10-50ms per validation depending on schema complexity)","Complex nested schemas may be difficult to define and maintain in ABAP","No built-in schema generation from ABAP data types; schemas must be manually defined","Validation errors may not provide detailed path information for deeply nested objects"],"requires":["JSON Schema definition for each tool parameter and resource output","ABAP 7.52+ with native JSON schema validation support"],"input_types":["JSON object (tool parameters or resource data)"],"output_types":["validation result (pass/fail with error details)"],"categories":["data-processing-analysis","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-sap-abap-mcp-server-sdk__cap_6","uri":"capability://memory.knowledge.mcp.resource.exposure.from.abap.data.sources","name":"mcp resource exposure from abap data sources","description":"Enables ABAP servers to expose data as MCP resources (files, database records, API responses) through a standardized resource interface. Resources are registered with metadata (name, description, MIME type, URI) and retrieved on-demand by MCP clients. The framework handles resource discovery (resources/list), retrieval (resources/read), and template expansion for parameterized resources, allowing AI clients to access ABAP data without direct database access.","intents":["Expose ABAP database tables or custom data structures as MCP resources for AI analysis","Provide parameterized resource templates (e.g., 'customer/{id}') for dynamic data retrieval","Allow AI clients to discover available data sources via resources/list"],"best_for":["Teams building AI agents that need read-only access to SAP data (customers, orders, materials)","Enterprises exposing business data to AI models without direct database access"],"limitations":["Resources are read-only by default; no built-in write capability (use tools for mutations)","Resource retrieval is synchronous; large datasets may timeout or exceed response size limits","No built-in pagination or streaming for large resources; must be implemented per resource","Resource templates support simple parameter substitution; no complex query logic"],"requires":["Custom server class implementing resource handlers","ABAP data source (table, view, function module, or API)"],"input_types":["resource URI with optional parameters"],"output_types":["resource content (text, JSON, or binary data with MIME type)"],"categories":["memory-knowledge","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-sap-abap-mcp-server-sdk__cap_7","uri":"capability://tool.use.integration.mcp.tool.exposure.from.abap.function.modules.and.custom.methods","name":"mcp tool exposure from abap function modules and custom methods","description":"Exposes ABAP function modules and custom server methods as MCP tools that AI clients can invoke. Tools are registered with input/output schemas, descriptions, and execution handlers. The framework handles tool discovery (tools/list), invocation (tools/call), parameter marshaling, and error handling, allowing AI models to execute ABAP business logic (create orders, update materials, run reports) as part of agentic workflows.","intents":["Expose ABAP function modules as callable tools for AI agents","Enable AI models to execute business logic (create/update/delete operations) in SAP systems","Define tool input/output schemas for type-safe AI-to-ABAP integration"],"best_for":["Teams building AI agents that need to perform actions in SAP systems (order creation, material updates)","Enterprises automating business processes through AI-driven tool invocation"],"limitations":["Tool execution is synchronous; long-running operations may timeout (default timeout typically 30-60s)","No built-in transaction management; tools must handle ABAP transaction logic internally","Tool parameters are limited to JSON-serializable types; complex ABAP structures require custom marshaling","No built-in rate limiting or quota management; requires custom implementation per tool"],"requires":["Custom server class implementing tool handlers","ABAP function module or method with defined input/output parameters","JSON Schema definitions for tool input and output"],"input_types":["tool name and JSON parameters"],"output_types":["tool execution result (JSON object or error)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-sap-abap-mcp-server-sdk__cap_8","uri":"capability://memory.knowledge.mcp.prompt.exposure.from.abap.templates.and.system.context","name":"mcp prompt exposure from abap templates and system context","description":"Exposes ABAP-generated prompts as MCP prompts that guide AI model behavior. Prompts can be static templates or dynamically generated based on ABAP system context (current user, business data, system configuration). The framework handles prompt discovery (prompts/list), retrieval (prompts/get), and argument substitution, allowing AI clients to use ABAP-provided instructions and context to improve model responses.","intents":["Provide AI models with SAP-specific instructions and context via MCP prompts","Dynamically generate prompts based on current ABAP system state (user role, business data)","Enable AI clients to discover available prompts and use them to guide model behavior"],"best_for":["Teams building AI agents that need SAP-specific domain knowledge and instructions","Enterprises customizing AI model behavior based on business context and user roles"],"limitations":["Prompts are read-only; no feedback mechanism for AI model to influence prompt generation","Prompt generation is synchronous; complex dynamic prompts may add latency","No built-in versioning or A/B testing of prompts; requires custom implementation","Argument substitution is simple string replacement; no complex templating logic"],"requires":["Custom server class implementing prompt handlers","Prompt template or dynamic generation logic in ABAP"],"input_types":["prompt name and optional arguments"],"output_types":["prompt text (string)"],"categories":["memory-knowledge","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-sap-abap-mcp-server-sdk__cap_9","uri":"capability://code.generation.editing.base.server.framework.with.lifecycle.hooks.for.custom.server.development","name":"base server framework with lifecycle hooks for custom server development","description":"Provides ZCL_MCP_SERVER_BASE abstract class that custom servers extend to implement MCP protocol handlers. Includes lifecycle hooks (initialize, shutdown, on_request) and abstract methods for resources, tools, and prompts. The framework handles protocol compliance, error handling, and session management, allowing developers to focus on business logic implementation without reimplementing MCP protocol details.","intents":["Build custom MCP servers without implementing full MCP protocol from scratch","Leverage framework lifecycle hooks for initialization and cleanup logic","Implement resources, tools, and prompts with minimal boilerplate code"],"best_for":["ABAP developers building MCP servers for the first time","Teams standardizing MCP server implementation patterns across multiple servers"],"limitations":["Abstract base class requires implementing all protocol methods; no optional feature support","Lifecycle hooks are synchronous; no async/await support for long-running initialization","Error handling is framework-level; custom error types must be mapped to JSON-RPC errors","No built-in logging or observability; requires custom implementation per server"],"requires":["ABAP class extending ZCL_MCP_SERVER_BASE","Implementation of abstract methods (resources, tools, prompts)"],"input_types":["MCP protocol requests (initialize, resources/list, tools/call, etc.)"],"output_types":["MCP protocol responses (capabilities, resources, tools, results)"],"categories":["code-generation-editing","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":32,"verified":false,"data_access_risk":"high","permissions":["SAP ABAP 7.52+ (or 7.02 with downport compatibility)","Access to ZMCP_* configuration tables with INSERT/UPDATE/DELETE permissions","Custom server class implementing ZCL_MCP_SERVER_BASE interface","HTTP request body containing valid JSON-RPC 2.0 message","Server instance with methods matching MCP protocol (initialize, resources/list, tools/call, etc.)","ABAP JSON parsing library (native to 7.52+)","ICF service configured with HTTP handler pointing to ZCL_MCP_HTTP_HANDLER","Configuration table entries mapping paths to server classes","ABAP 7.52+ with native JSON support","Properly structured ABAP types (classes or structures) for serialization"],"failure_modes":["Configuration table changes require manual activation; no hot-reload without system restart","Server class must exist in ABAP system before factory can instantiate it","No built-in versioning or rollback mechanism for configuration changes","No support for batch request optimization; processes requests sequentially","Error responses follow JSON-RPC 2.0 spec but may not include ABAP-specific context in error messages","Notification handling (requests without id) discards responses; no logging of notification outcomes by default","Path-based routing is simple string matching; no regex or pattern-based routing","Server lookup requires configuration table access on every request; adds latency (~5-10ms)","No built-in caching of server configuration; configuration changes require manual refresh","No support for dynamic path parameters beyond simple path segments","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.5,"ecosystem":0.39999999999999997,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:04.048Z","last_scraped_at":"2026-05-03T14:00:18.053Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=sap-abap-mcp-server-sdk","compare_url":"https://unfragile.ai/compare?artifact=sap-abap-mcp-server-sdk"}},"signature":"C9PehIxf5S97jLpjfIZGsXdXGgpCGKgxALFe+DYySv+B+1+3ESn5Xf0HesJxypeToVIMjJJMMCnWDF7lsJgHDg==","signedAt":"2026-06-19T23:18:24.035Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/sap-abap-mcp-server-sdk","artifact":"https://unfragile.ai/sap-abap-mcp-server-sdk","verify":"https://unfragile.ai/api/v1/verify?slug=sap-abap-mcp-server-sdk","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}