As a gRPC API consumer
I want to be able to provide some data, it's cryptographic signature and a public key using a gRPC endpoint
So that I can verify that the associated private key was used to sign the data

Given crypto_controller.rs already exists and interfaces with crypto_service.rs
When adding key value support to gRPC and MCP
When use crypto_controller.rs as an example of how to integrate with crypto_service.rs

Given pointer_handler.rs already exist
When adding crypto_handler.rs
Then use pointer_handler.rs as an example
And integrate with crypto_service.rs
And create/use the crypto.proto as defined below:


```
syntax = "proto3";

package crypto;

service CryptoService {
  rpc Verify(VerifyRequest) returns (VerifyResponse);
}

message Verify {
  string data = 1;
  string signature = 2;
  bool verified = 3;
}

message VerifyRequest {
  string public_key = 1;
  repeated Verify verify = 2;
}

message VerifyResponse {
  string public_key = 1;
  repeated Verify verify = 2;
}
```

Given pointer_tool.rs already exist
When adding crypto_tool.rs
Then use crypto_tool.rs as examples
And integrate with crypto_service.rs

Implementation Notes

- Place any unit tests at the bottom of the same file as the associated production code
- Increment patch version of anttp package in Cargo.toml
- Create a copy of this issue description and save to /spec using the name of this issue as the filename (with lower underscore case, starting with the 5 char padded issue number, e.g. 00001_issue_title.txt)
- Update unit tests to validate the changes
